[r.in.poly fails to read text input file on Windows/CMD line]
On Fri, Aug 14, 2009 at 3:52 PM, Peter Brooks<peter@timedworld.com> wrote:
No, I think it is whitespace... I'm trying to use the 'cmd >' field
in the 'GRASS GIS Layer Manager' (the new wxPython GUI). I guess
this is what a Windows user would try to do
I tried adding a space to the folder name (= 'c:\nc external'),
forward slashes don't help but speech or quote marks do.
(I think the same thing happens with all r.in commands if they are
looking for external files - is this to be expected?)
Using the GRASS Command line utility (DOS shell type interface):
GRASS 6.4.0svn (North-Carolina)> cd c:/nc external
The system cannot find the path specified.
GRASS 6.4.0svn (North-Carolina)> cd c:\nc external
(works ok)
@devs:
Perhaps we need some more G_convert_dirseps_*() magic?
[r.in.poly fails to read text input file on Windows/CMD line]
I have checked at the r.in.poly source code, the problem does
not seem to be there. The path is passed to fopen() verbatim.
what version/revision of 6.4.0svn is this? is it the latest?
ISTR that Martin&Glynn had fixed this -- wxGUI now uses a
python parser which understands shell quoting on the Cmd> line.
But that might only be present in the very latest build.
---------- Forwarded message ----------
From: Peter Brooks <peter@timedworld.com>
Date: Sat, Aug 15, 2009 at 11:45 AM
Subject: Re: [GRASS-dev] Re: [GRASS-windows] No such file or directory
To: Hamish <hamish_b@yahoo.com>
Cc: grass-windows@lists.osgeo.org
The 'About' window says
GRASS GIS 6.4.0svn (2009)
GIS Library Revision 37101 (2009-05-10)
I downloaded and installed on 02-Aug.
Cheers
Peter
On 14 Aug 2009 at 16:54, Hamish wrote:
[r.in.poly fails to read text input file on Windows/CMD line]
I have checked at the r.in.poly source code, the problem does
not seem to be there. The path is passed to fopen() verbatim.
what version/revision of 6.4.0svn is this? is it the latest?
ISTR that Martin&Glynn had fixed this -- wxGUI now uses a
python parser which understands shell quoting on the Cmd> line.
But that might only be present in the very latest build.
