[GRASS-dev] g.mremove: adding 'map name exclusion pattern' option

[Huidae Cho]

Markus,

I think it's good time to remove redundant modules and "sync" g.mlist and
g.mremove parameters before releasing 7.0. Are there missing features from
g.mlist/g.mremove that g.list/g.remove has?

Huidae


On Fri, May 2, 2014 at 10:47 AM, Markus Neteler <neteler at osgeo.org> wrote:

> On Fri, May 2, 2014 at 3:01 AM, Huidae Cho <grass4u at gmail.com> wrote:
> > Well, the g.mremove interface looks convenient, but can be dangerous
> also.
> > For example, yesterday, I almost deleted my raster files by using the
> > positional parameter thing while trying to delete all my temporary
> vectors.
> >
> > g.mremove tmp*
> >
> > Whops! Did I want to delete tmp* rasters or vectors? I forgot to add
> vect=
> > and my tmp* rasters were listed. Thanks to the -f option.
>
> The easiest workaround is that we reorder the parameter list. At time we
> have
> rast = 1st = default.
>
> See
> http://grass.osgeo.org/grass71/manuals/g.mremove.html
>
> Putting there, say, "label" will enforce the user to have to set rast=
> for deleting raster maps. This would require no extra efforts and
> minimize the risk except for those using labels (so we could even add
> a dummy parameter there. Or select another rather unknown parameter
> from that list to become the first in the list).
>
> Markus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20140509/dda76c28/attachment.html>