1. constructed configuration files using override It seems very complicated. How does it use?
2. name of configuration file These names follow custom. gtags.conf: resolv.conf, man.conf, ftpd.conf, ... .globalrc: .bashrc, .vimrc, .elvisrc, ... What kind of problem is there? 3. use configuration options instead of environment variables Do you mean that we should use gtags_options (or global_options) configuration variable instead of GTAGS_OPTIONS environment variable? You are right. It corresponds to htags_options well. 4. ability to set and get configuration options, dump, ... I don't know about 'git config'. Would you explain it concrelely? 2014-02-28 21:02 GMT+09:00 Leo Liu <[email protected]>: > On 2014-01-22 00:40 +0800, Jason Hood wrote: > > Find attached a patch that implements both GLOBAL_OPTIONS (marking > > GTAGSTHROUGH as deprecated) and --color=never|always|auto (-C and > > --color are the same as --color=auto) for 6.2.10 > > I wonder if it is time to have a configuration hierarchy, for example: > > GTAGSROOT/.globalrc -> $HOME/.globalrc -> SYSTEM_DIR/globalrc -> program > defaults > > in the order of most to least specific. The configuration is constructed > by all those files and allow options in more specific files to override > less ones. > > The config file doesn't need to be named .globalrc or globalrc but don't > use two names i.e. .globalrc and gtags.conf. > > Keep environment variables to minimal and prefer configuration options. > > Give 'global' ability to set and get configuration options, dump > configuration for debugging etc. > > A good practical example is 'git config'. > > Thoughts? > > Leo > > _______________________________________________ > Bug-global mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/bug-global > -- Shigio YAMAGUCHI <[email protected]> PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3
_______________________________________________ Bug-global mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-global
