bug-global
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC] New mechanism for specifying options


From: Shigio YAMAGUCHI
Subject: Re: [RFC] New mechanism for specifying options
Date: Fri, 25 Apr 2014 15:17:31 +0900

While implementing the -U (--use-default) option,
I recognized my mistake. The option was a halfway
and hard to use. First of all, what cannot be used
without an option cannot be called 'default options'.
So, I would like to change the solution.

I withdraw the followings:
o -U (--use-default) option.
  It is a halfway and hard to use.
o GLOBAL_OPTIONS environment variables.
  It is dangerous.

The result is as follows.

command         default options    variable name
------------------------------------------------
global(1)       not available      -
gtags(1)        available          GTAGS_OPTIONS
htags(1)        available          HTAGS_OPTIONS
------------------------------------------------

To use default options for global(1), you should
use something like alias or function of the shell
instead. For example,

$ alias global='global --color=always'

Global(1) itself does not offer any means for it.
About GTAGS_OPTIONS and HTAGS_OPTIONS, there is
no problem, I think.

Any comment?



2014-04-21 9:52 GMT+09:00 Shigio YAMAGUCHI <address@hidden>:
I would like to change the RFC as follows.

1. Addition of -U option

The default options are used only when -U (--use-default)
option is specified. It is provided for the each command.

$ global -x main                # without default options
$ global -xU main               # use default options

The reason is for preventing bad influences to applications
which use GLOBAL. For example, if GLOBAL_OPTIONS is set to '-G'
then the following command will fail.

global "<extended regular _expression_>" ...

Since there are many tools which use GLOBAL, we should not add
changes which break what are working now.

--
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663  C4B6 3CA5 BBB3 57BE DDA3

reply via email to

[Prev in Thread] Current Thread [Next in Thread]