[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ‘global -c’ and $GTAGSLIBPATH
From: |
Shigio YAMAGUCHI |
Subject: |
Re: ‘global -c’ and $GTAGSLIBPATH |
Date: |
Fri, 17 Jun 2011 08:11:46 +0900 |
Hi,
> $Bfb%^%M(Blobal -c$Bfb(B<99> doesn$Bfb%`%f(B honor $GTAGSLIBPATH and
> just bails out when not
> $Bfb%^%#(BTAGS$Bfb(B<99> file is found under $PWD or its ancestors.
>
> I think it would be more convenient if it would honor $GTAGSLIBPATH and
> fail only when there$Bfb%`%d(B no $Bfb%^%#(BTAGS$Bfb(B<99> file under
> $PWD *and* not $Bfb%^%#(BTAGS$Bfb(B<99> file
> under any of the directories in $GTAGSLIBPATH.
If GTAGS is not found under $PWD or its ancestors, it should fail.
Since it is a fundamental specification of GLOBAL, it is hard to change it.
At such time, you should use GTAGSROOT environment variable, I think.
$ mkdir nullproject # make null project
$ cd nullproject
$ gtags
$ pwd
/home/you/nullproject
$ GTAGSROOT=/home/you/nullproject global -x ...
But if your idea means that global -c should read GTAGSs in $GTAGSLIBPATH
if no matched tag name is found in the GTAGS under $PWD or its ancestors,
it might be useful. That is consistent.
--
Shigio YAMAGUCHI <address@hidden>
PGP fingerprint: D1CB 0B89 B346 4AB6 5663 C4B6 3CA5 BBB3 57BE DDA3