Path to this page:
Subject: CVS commit: pkgsrc/devel/global
From: Thomas Klausner
Date: 2016-12-30 01:39:30
Message id: 20161230003930.5F3F2FBA6@cvs.NetBSD.org
Log Message:
Updated global to 6.5.6.
Version 6.5.6 - December 19 2016
[CHANGES]
New facilities:
o htags-server: New --retry[=n] option.
If the port is already in use, retry n times with incrementing the port number.
The default of n is 20.
o htags: Changed the format of function header (--show-position) to make copying
text easier.
o geco.rc: Added 'fzf' as a selector candidate.
o gtags: New configuration variable 'gtags_hook'.
gtags_hook=<command line>
Specify a command line which should be executed at the beginning of gtags(1).
Leading "./" in any path is always means the project root directory, since
gtags(1) is always invoked there.
GTAGS_COMMANDLINE environment variable (read only)
You can get the effective command line of gtags(1) from the hook. It includes
both $GTAGS_OPTIONS and real arguments.
[Usage]
You can update 'gtags.files' before gtags(1) read it.
[gtags.conf]
+----------------------------------------
|...
|:gtags_hook=find src lib -print >gtags.files:
You can refer the effective arguments of gtags(1) from the hook using
environment variable GTAGS_COMMANDLINE.
[gtags.conf]
+----------------------------------------
|...
|:gtags_hook=./gen.sh:\
|:GTAGS_OPTIONS=-c:\
[gen.sh]
+----------------------------------------
|#!/bin/sh
|echo ">>> $GTAGS_COMMANDLINE" # show effective command line
$ gtags -O
>>> gtags -c -O
$ _
[INCOMPATIBLE CHANGES]
o htags: Now --cvsweb option always insert 'view=log' to the generated URLs.
Because it seems to be almost always a desirable specification.
[FIXED BUGS]
o gtags: Gtags often aborts with a message "buffer overflow. \
strlimcpy" when
it encounters a long token (> 152 bytes). Now gtags always ignores it with
a message "symbol name is too long. (Ignored)".
o htags: Old packages included two CGI scripts (completion.cgi, global.cgi)
generated in the release manager's machine by mistake. They have some literal
path like '/opt/local/bin/perl' which works only with MacPorts.
Now, they are generated in the target (your) machine.
Files: