[GRASS-user] "g.region -cd" creates an unusable WIND file instead of printing error messages

Can anybody confirm that running the (irrational to me) command
"g.region -cd" creates an (almost empty) unusable WIND file? Is this a
bug that should be reported?

# issue irrational command
g.region -cd

# verify broken WIND file
g.region -p

ERROR: region for current mapset is invalid
       <north field missing>
       run "g.region"

# attempt to restore region fails, e.g.
g.region rast=StudyArea -pa

ERROR: region for current mapset is invalid
       <north field missing>
       run "g.region"

Kind regards, Nikos
-------------------

Details

While testing *.region.* qgis-grass tools I saw that in r.region.region
one can select both "Set from current region" and "Set from default
region". Before writing down my comments about this I wanted to ensure
that this is also NOT possible (or rational) to use in grass itself. A
report with respect *.region.* qgis-grass tools will follow in a few
days.

On Mon, 2009-06-22 at 21:40 +0300, Nikos Alexandris wrote:

Can anybody confirm that running the (irrational to me) command
"g.region -cd" creates an (almost empty) unusable WIND file? Is this a
bug that should be reported?

Probably my "default" region is empty which in turn results in an
(almost) empty WIND file! Not sure... :-?

g.region -d "breaks" the WIND file.

Anyhow, I also confused g.region with r.region. The issue with
r.region.region (a qgis-grass tool) issue will be reported in the
respective QGIS locations. Sorry for the traffic.

Nikos