[GRASS-dev] g.list in G71

Anna Petrášová kratochanna at gmail.com
Tue Oct 28 12:48:19 PDT 2014


On Tue, Oct 28, 2014 at 1:05 PM, Huidae Cho <grass4u at gmail.com> wrote:

> Hi,
>
> IMO, printing fully-qualified names by default can be too much information
> in terminal and make it uncomfortable to read map names only. Currently, it
> prints fully-qualified names whenever maps cannot be identified by their
> unqualified names (e.g., two maps with the same name in multiple mapsets).
>

Maybe there was a discussion already about this, but another option is to
use -p as default (so that we actually see the mapsets) and add new flag
 -g as shell script style? So that the default would be the same as g.list
before?

If I should decide between with/without mapset (the original question), I
think by default the mapset should be printed. The mapset information is
more important for me than the clutter it causes.

Anna


> Huidae
>
> On Tue, Oct 28, 2014 at 5:47 AM, Luca Delucchi <lucadeluge at gmail.com>
> wrote:
>
>> On 28 October 2014 10:44, Martin Landa <landa.martin at gmail.com> wrote:
>> > Hi,
>> >
>>
>> Hi
>>
>> > 2014-10-27 21:01 GMT+01:00 Martin Landa <landa.martin at gmail.com>:
>> >> I would suggest to print fully-qualified names by default. Any
>> opinion? Martin
>> >
>> > If you agree I would vote for reverting logic of -m flag to
>> >
>> > Print unqualified map names (without mapsets)
>> >
>> > ?
>> >
>>
>> +1
>>
>> > Martin
>> >
>>
>>
>> --
>> ciao
>> Luca
>>
>> http://gis.cri.fmach.it/delucchi/
>> www.lucadelu.org
>> _______________________________________________
>> grass-dev mailing list
>> grass-dev at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
> _______________________________________________
> grass-dev mailing list
> grass-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20141028/4c3377aa/attachment.html>


More information about the grass-dev mailing list