Controlled vocabulary files may contain a list of command line options that are mandatory.
Example: #options --recursive --filebrowser thunar always uses functions recursive and opens results in thunar (instead of a different default browser).
FIXXME:
- What about contradicting CLI options?
- example 1:
--filebrowser thunar in .filetags and --filebrowser geeqie in command line?
- example 2:
--tagtrees-depth 3 in .filetags and user just wants to tag a file (which does not allow/need tagtrees at all and results in an error)
Controlled vocabulary files may contain a list of command line options that are mandatory.
Example:
#options --recursive --filebrowser thunaralways uses functions recursive and opens results in thunar (instead of a different default browser).FIXXME:
--filebrowser thunarin .filetags and--filebrowser geeqiein command line?--tagtrees-depth 3in .filetags and user just wants to tag a file (which does not allow/need tagtrees at all and results in an error)