[GRASS-dev] [GRASS GIS] #3751: Logical operators for g.search.modules

[GRASS GIS]

#3751: Logical operators for g.search.modules
------------------------------+-------------------------
 Reporter:  Nikos Alexandris  |      Owner:  grass-dev@…
     Type:  enhancement       |     Status:  new
 Priority:  normal            |  Milestone:
Component:  Default           |    Version:  unspecified
 Keywords:  g.search.modules  |        CPU:  Unspecified
 Platform:  All               |
------------------------------+-------------------------
 Following are
 [https://trac.osgeo.org/grass/search?q=g.search.modules&noquickjump=1&ticket=on
 results searching for `g.search.modules`] tickets:  #3624, #3583, #3405,
 #3341, #3149, #386, #151.

 Considering these and the fact that
 [https://grass.osgeo.org/grass76/manuals/g.search.modules.html
 g.search.modules] features currently three flags (`-a`, `-n` and `-k`) to
 minapulate the retrieval of modules based on (combination) keywords,

 what about using parameters like `subset=` based on pre-defined sets that
 list modules **and/or** `selection=` based on logical operators to combine
 the requested keywords?

 Examples of describing the inerface:

 {{{
 subset Subset of available modules
        options: all, core, addons, other(?)
        default: core
 }}}

 or even (which might overlap the functionality of `keywords=`?)

 {{{
 subset Subset of available modules
        options: all, core, addons, generic, raster, vector, miscellaneous,
 temporal
        default: core
 }}}

 (under options also things like the
 [https://grass.osgeo.org/grass76/manuals/topics.html topics index] if
 topis are not covered by the
 [https://grass.osgeo.org/grass76/manuals/keywords.html keywords index] ?)

 and

 {{{
 selection Define selection of keywords
           options: and,or,not,xor,xnor,nand
           default: or
 }}}

 (obviously, excluding operators which would not make sense).

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/3751>
GRASS GIS <https://grass.osgeo.org>