|
From: | Marcus Harnisch |
Subject: | Re: Python 3 and pygments-parser |
Date: | Thu, 16 May 2024 00:42:46 +0200 |
Hi Marcus,
I confirmed that the problem is reproduced.
I have made a new entry to the 'Known bugs' list.
Thank you for the report.
[https://www.gnu.org/software/global/bugs.html]
o Pygments plug-in parser with python3 does not work, if 'ctagscom' is not set.
If it is not set, default path obtained by configure script should be used.
$ cat > gtags.conf
default:\
:ctagscom=:\
:langmap=C\:.c.h:\
:gtags_parser=C\:/usr/local/lib/gtags/pygments-parser.la:
$ gtags
$ global -x '.*'
$ _ # no tags
Regards,
Shigio
On Mon, May 13, 2024 at 5:04 PM Marcus Harnisch
<marcus.harnisch@verilab.com> wrote:
>
> Hi Shigio
>
> On Sat, May 11, 2024 at 5:35 AM Shigio YAMAGUCHI <shigio@gnu.org> wrote:
>>
>> $ cat gtags.conf
>> default:\
>> :ctagscom=/opt/local/bin/uctags:\
>> :langmap=C\:.c.h:\
>> :gtags_parser=C\:/usr/local/lib/gtags/pygments-parser.la:
>
>
> The important difference, which exposes the bug, is your explicit configuration of ctagscom. Leave it undefined and rely on whatever UNIVERSAL_CTAGS has been configured to. Only if ctagscom is empty, you will see a comparison between b'' (empty bytearray) and '' (empty string).
>
> Best regards,
> Marcus
--
Shigio YAMAGUCHI <shigio@gnu.org>
PGP fingerprint:
26F6 31B4 3D62 4A92 7E6F 1C33 969C 3BE3 89DD A6EB
[Prev in Thread] | Current Thread | [Next in Thread] |