shrug, `-g` is mainly used for shell script output, I think it would
be better update `r.info` and `v.info` to follow this logic, g.region
is an exception. You are going to the opposite direction!
2011/11/14 svn_gr...@osgeo.org:
Author: hamish
Date: 2011-11-13 22:49:25 -0800 (Sun, 13 Nov 2011)
Martin wrote:
shrug, `-g` is mainly used for shell script output,
I think it would be better update `r.info` and `v.info` to
follow this logic, g.region is an exception. You are going to
the opposite direction!
AFAIR g.region was the original, using -g to display region
bounds in shell script
Hi,
sometimes it is a good idea to rethink existing design decisions and
re-implement it in a better way. As you stated the shell style output
was added to the modules successively without having a specific design
rule, but imitating g.region. Maybe its a good time to change this, at
least in
Hamish wrote:
Martin wrote:
shrug, `-g` is mainly used for shell script output,
I think it would be better update `r.info` and `v.info` to
follow this logic, g.region is an exception. You are going to
the opposite direction!
AFAIR g.region was the original, using -g to display region
On Mon, Nov 14, 2011 at 11:51 AM, Markus Metz
markus.metz.gisw...@googlemail.com wrote:
Quickly glancing at grass 4.0, g.region -p prints the current region,
whereas the -g flag is there to print in shell style. What exactly is
printed in shell style is obviously module-dependent (emphasis on