This may have been mentioned a month ago? but I notice that v.proj
(& r.proj?) ignores overwrite settings and overwrites a map without
needing the --o flag set.
Hamish
This may have been mentioned a month ago? but I notice that v.proj
(& r.proj?) ignores overwrite settings and overwrites a map without
needing the --o flag set.
Hamish
Hamish wrote:
This may have been mentioned a month ago? but I notice that v.proj
(& r.proj?) ignores overwrite settings and overwrites a map without
needing the --o flag set.
Neither of them have gisprompt settings for their options.
--
Glynn Clements <glynn@gclements.plus.com>
Hamish:
> This may have been mentioned a month ago? but I notice that v.proj
> (& r.proj?) ignores overwrite settings and overwrites a map without
> needing the --o flag set.
Glynn:
Neither of them have gisprompt settings for their options.
r.proj didn't, but v.proj does.
v.proj uses G_define_standard_option(G_OPT_V_OUTPUT) which sets:
Opt->gisprompt = "new,vector,vector";
You do get the "WARNING: file exists and will overwritten" message.
(but by the time you read that you have already started writing, so no
way out)
?
Hamish