Replace g.list/g.remove with g.mlist/g.mremove
|Reported by:||hcho||Owned by:||hcho|
|Keywords:||g.list, g.remove, g.mlist, g.mremove||Cc:|
I propose to replace the old g.list and g.remove modules with enhanced g.mlist and g.mremove. This will break backward compatibility because of changes in API and output behavior.
By default, g.mlist prints outputs in a machine friendly format (e.g., not directed to a paper) while g.list prints in human readable format using a pager. g.mlist -p does pretty printing. g.mlist additionally has pattern=, exclude=, separator=, region=, and output= options.
g.mremove has only one option for specifying data types to delete while g.remove has as many options as available data types. Since the first option in g.remove is rast=, the user can delete raster maps by mistake when s/he actually intended to delete vector maps. With g.mremove, type= is required and the user must specify data types explicitly. g.mremove additionally has pattern= (for map names or search pattern) and exclude= options.
Please let me know if you have good reasons to keep the old g.list and g.remove. Otherwise, I suggest to replace g.list and g.remove with g.mlist and g.mremove before 7.0 release.