Re: global doesn't respect functions declared as static

[Mohammed Sadiq]

> On February 23, 2017 at 3:57 PM Shigio YAMAGUCHI <address@hidden> wrote:
> 
> Hi,
> 
Hi

> Sorry but --from-here is not such option. Normally it is not used on the 
> command line.
> I am sorry that the description of the online manual is inadequate.
> 
I just pasted the output of what ggtags.el would run inside GNU Emacs. I simply 
ran those
in command line to see why it was happening. And reported.

> > Alternatly, if it is hard to track the return type of functions, the result
> > can be sorted that the first item shown is from the same file (when there 
> > is a
> > match).
> > 
> > Ie, The result then would be:
> > src/my-source.c
> > src/my-first-source.c
> 
> Rather, --nearness option has a close meaning to your suggestion.
> The --nearness option displays tags closer to the current position first.
> However, at present, only directory can be specified as an argument.
> 
> Present specification: --nearness=
> 
> How about changing the spec to accept a file as an argument of it?
Good enough. Though It might not help everybody, but just me.
> 
> New specification: --nearness=
> 
> If a file is specified, global gives it the highest priority.
> 
> Does this meet your requirements?

Right now, what ggtags does is find all references and visit the location of the
first reference returned by global. This would be what most editors (or IDEs) 
would do. 
Because checking for '--nearness' with some file and then doing '--frome-here' 
if --nearness fails would be twice as slow, especially for very large codebase.

The simpler one what IDEs would benefit shall be, list the matches from the 
same file
first. Then the rest (when --from-here is given).

Hope you can understand.
Thanks