[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC] New mechanism for specifying options
From: |
Leo Liu |
Subject: |
Re: [RFC] New mechanism for specifying options |
Date: |
Fri, 28 Mar 2014 15:11:43 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (CentOS 6.5) |
On 2014-03-27 11:29 +0800, Shigio YAMAGUCHI wrote:
> 3. Three configuration variables
>
> Adding three configuration variables of the same name
> as the environment variables described in 1.
>
> Example:
> [gtags.conf]
> :GLOBAL_OPTIONS=--ignore-case:\
> :GTAGS_OPTIONSS=--idutils:\
> :HTAGS_OPTIONS=-gs:...
>
>
> Each environment variable is given more priority than configuration
> variable of the same name. 'htags_options' will be deprecated.
>
> This rule should be applied to any environment variable used in GLOBAL
> someday, I think.
>
> Any comment?
Thanks for these features.
But I would much prefer a way to set things on a per project (directory)
basis. Environment variables are global. If I setenv for perl projects,
they might interfere with my php projects.
I have made ggtags¹ automatically use .globalrc or gtags.conf at current
project root i.e. where GTAGS is so that I don't have to reset GTAGSCONF
for every project. It turns out I use this feature on almost every
project at least for ignoring certain subdirectories to cut down
uninteresting matches.
Leo
Footnotes:
¹ https://github.com/leoliu/ggtags