[GRASS-dev] erratic behavior of v.in.ascii with WinGRASS

Moritz Lennert mlennert at club.worldonline.be
Wed Feb 6 04:38:03 EST 2008


On 05/02/08 17:17, Michael Barton wrote:
> 
> On Feb 5, 2008, at 8:48 AM, Moritz Lennert wrote:
> 
>>
>> I would rather guess that depending on how the command line was 
>> formulated, i.e. where the fs=| is placed, the command runs correctly 
>> with the default values (i.e. '|' as seperator) or doesn't.
>>
> 
> Not in the case of my Mac gui crash. Exact same command argument order 
> (in gui):
> 
> fs=|   + different number of fields in different records (i.e., data 
> file format bad) = crash TclTk
> fs=|   + same number of fields in all records (i.e., data file format 
> good) = OK
> fs="|" + different number of fields in different records (i.e., data 
> file format bad) = OK
> fs=,   + different number of fields in different records (i.e., data 
> file format bad) = OK
> 

As Glynn said:
> The Tcl/Tk GUI doesn't use the shell to execute commands, so it
> shouldn't be an issue there.

So, since all the above are done via the gui my guess seems to be 
totally off anyhow...

IIRC, you said that you cannot reproduce this behaviour on the command 
line, i.e. even the first case works on the command line ?

Moritz


More information about the grass-dev mailing list