Hello,
> Please consider offering option to specify the path to the data-base to
global:
>
>     global  --dbpath <path to data base>
>
> Motivation:  with above feature, one could issue following command inside
gvim:
>
>     :Gtags  --dbpath <path>  --gtagsconf <rcfile>  --gtagslabel <prj_1>
>
> and thereby use two gvims to explore two projects
>
> Thanks,
>
> --Suresh

I can seldom agree.

One of the merit of GLOBAL is the ability to locate the database by itself.
If you are in a project, global(1) locates the database instead of you.
The greatest weak point of this method was having to make tag files
in the project. But it was solved by 'obj' directory.
Now, use of GTAGSROOT and GTAGSDBPATH is not recommended.
So, I can seldom approve of the --dbpath option.



2014-06-16 8:34 GMT+09:00 Suresh Govindachar <[email protected]>:

>
> Hello,
>
> Please consider offering option to specify the path to the data-base to
> global:
>
>     global  --dbpath <path to data base>
>
> Motivation:  with above feature, one could issue following command inside
> gvim:
>
>     :Gtags  --dbpath <path>  --gtagsconf <rcfile>  --gtagslabel <prj_1>
>
> and thereby use two gvims to explore two projects
>
> Thanks,
>
> --Suresh
>
> _______________________________________________
> 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

Reply via email to