OK. This change will probably be in the next release.
I think there was a mistake in the specifications.
Thanks,
Shigio
2020年4月24日(金) 15:56 Marcus Harnisch :
>
> Hi Shigio
>
> That would definitely be a good thing to have (including the corresponding
> short options). In my case an additional op
Hi Shigio
That would definitely be a good thing to have (including the corresponding
short options). In my case an additional options filter will still be
necessary so that --single-update won't trigger rebuilding the file list.
Thanks,
Marcus
On Fri, Apr 24, 2020 at 3:40 AM Shigio YAMAGUCHI w
> Something (perhaps gtags-mode) calls gtags with the --config option before
> the actual scan. This in turn invokes gtags_hook, too.
> I am already maintaining a list of options in my gtags_hook that should bypass
> generating the file list, e.g --help, --dump, --single-update. Now adding
> --con
Still investigating... It looks like the issue isn't caused by the actual
gtags invocation. Something (perhaps gtags-mode) calls gtags with the
--config option before the actual scan. This in turn invokes gtags_hook,
too. I am already maintaining a list of options in my gtags_hook that
should bypas
Hello,
Could you please give me a reproduce method to understand the problem?
Thanks,
Shigio
2020年4月21日(火) 22:26 Marcus Harnisch :
>
> Hi Shigio
>
> It's been a while but related to this, I was wondering if GTAGS_COMMANDLINE
> isn't supposed to include ‘--single-update’ when specified. In my hoo
Hi Shigio
It's been a while but related to this, I was wondering if GTAGS_COMMANDLINE
isn't supposed to include ‘--single-update’ when specified. In my hook
script, I am using this to determine whether to start a long-running
process of rebuilding the file list.
It looks like the switch doesn't ma
Hi Shigio
Sure, GTAGS_COMMANDLINE would be fine, too. This could be scanned by the
hook script with getopts(1) in case access to individual elements is needed.
In my case the application could be to determine the file name that has
been specified with -f and use that to dump the output generated b
Hi,
> However, I am not entirely happy from a usability perspective.
> In particular it would be helpful to have the hook know about all active
> command line options, even those passed in by GTAGS_OPTIONS (e.g. for
> determining the -f parameter). This doesn't seem possible at the moment,
> as the
Hi Shigio
I played with the gtags_hook and managed to generate a file list with the
help of rsync(1), so I can take full advantage of the powerful syntax of
its --exclude-from option. This works quite well as a proof-of concept
generic hook script, that could be installed systemwide.
However, I am
Good to know. I wasn't aware of the coexistence of skip with gtags.files.
Thanks
Marcus
On Wed, Oct 12, 2016 at 10:50 AM, Shigio YAMAGUCHI wrote:
> Sure. You can get 'skip list' from the hook.
>
> [gen.sh]
> gtags --conf=skip
>
> The skip list is always active even if you are using 'gtags.files
Sure. You can get 'skip list' from the hook.
[gen.sh]
gtags --conf=skip
The skip list is always active even if you are using 'gtags.files'.
Regards,
Shigio
2016-10-11 17:11 GMT+09:00 Marcus Harnisch :
> Hi Shigio
>
> That would be a very powerful facility indeed and certainly enable me to
> a
Hi Shigio
That would be a very powerful facility indeed and certainly enable me to
achieve what I intend. Perhaps you could consider passing the skip list
(perhaps any config variables that make sense) from gtags.conf to the hook
by means of environment variables, so users could reference a standa
Hi,
I will add new config variable 'gtags_hook' for gtags(1).
gtags_hook (command line)
Specify a command line which should be executed before the gtags's
job. "./" in it always means the project root directory, since
gtags is always invoked there.
This hook might realize your requirement.
13 matches
Mail list logo
