#3481 closed defect (invalid)
m.cogo (and others most likely) fail in Grass 7 under OS X if output path contains spaces
| Reported by: | fgfletcher | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Default | Version: | 7.0.0 |
| Keywords: | path quoting, m.cogo | Cc: | |
| CPU: | OSX/Intel | Platform: | MacOSX |
Description
Occurs here under Mac OSX 10.12.6 when using GRASS 7 as bundled into QGIS 2.18.15-3.
m.cogo, and most likely others, fail under OS X if the output path contains spaces. Input path seems unaffected.
So trying to send output into ~/my files/test_data/ results in an error message that files/test_data is not legit.
OS X allows spaces (and other non-alphanumeric chars) within directory (folder) or file names.
Consequently in OSX paths need to be "quoted" for Unix compatibility; I suspect that is what is missing.
Change History (6)
comment:1 by , 6 years ago
comment:2 by , 6 years ago
Thanks to the quick feedback.
Sounds like it must on the QGIS side. I'll pass my report on to them.
Many thanks.
follow-up: 5 comment:3 by , 6 years ago
Confirming that problem is in QGIS, not GRASS. Ran GRASS 7.2.2 directly and m.cogo's handling of spaces in file paths works OK. In QGIS 2.18.5 m.cogo, and others, quote input file paths, but do not quote output file paths. A workaround is to edit the output file path in place as displayed in the m.cogo dialog so as to include quotes. Problem has been reported to QGIS.
comment:4 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:5 by , 6 years ago
Replying to fgfletcher:
Problem has been reported to QGIS.
Please add the reference here for a better cross-linking among the projects. Thanks!
Replying to fgfletcher:
If m.cogo is called directly from within GRASS, m.cogo accepts output paths with spaces. Please provide an example with spaces in the output path that does not work when called within GRASS directly.
Otherwise it is a bug of QGIS, and ...
... in the QGIS interface to GRASS.