Anna wrote:
> This doesn't seem related. I explained the problem in the
> mail above but I can try to explain it more clearly if needed.
sorry, I reread you post and it was clear enough. the confusion
was all mine.
> Here is the ticket:
> http://trac.osgeo.org/grass/ticket/1633
it seems a bit s
Hi,
On Sun, Sep 9, 2012 at 1:15 PM, Hamish wrote:
> Hi,
>
> does this have to do with parsing the vector/$MAP/dbln file?
>
> There was an unfortunate thing in the 6.x format spec of that file where
> space was used as the delimiter and it was impossible to fix for spaces
> in the path, since the
Hi,
does this have to do with parsing the vector/$MAP/dbln file?
There was an unfortunate thing in the 6.x format spec of that file where
space was used as the delimiter and it was impossible to fix for spaces
in the path, since the result would always be ambiguous. In GRASS 7 I
changed the delim
On Tue, Sep 4, 2012 at 2:01 PM, Anna Kratochvílová
wrote:
...
> Problem occurs when calling this (line 194, dbmgr/manager.py in grass64)
...
> I recently added the fs parameter to be able to open data which
> contain | character by changing the separator in preferences. On
> Windows it is causing
On Tue, Sep 4, 2012 at 11:04 AM, Markus Neteler wrote:
> Hi,
>
> when loading "roadsmajor" of NC on various windows machines (with
> and without white space in the grassdata path, we get
>
> Error:
> 'columns' is not recognized as an internal or external command,
> operable program or batch file
>
Hi,
when loading "roadsmajor" of NC on various windows machines (with
and without white space in the grassdata path, we get
Error:
'columns' is not recognized as an internal or external command,
operable program or batch file
[OK]
Then the attrib. manager opens but it remains empty.
Maybe here?
