Shigio-san,
Thanks for your prompt reply and your help here.
I made the change /usr/local/share/gtags/script/pygments_parser.py as
you suggested,
and did the same test, however it did not help unfortunately.
I got the same result before the change.
I also confirmed that /usr/local/share/gtags/script/pygments_parser.py
is called and executed.
The cause of the problem was not in Universal Ctags, but in my insufficient
bug fixes for the following issues:
Universal Ctags: Don't read config files; New 'ctagsoptfile' configurati
Date: Fri, 07 Apr 2023 13:07:07 +0200
The workaround is still valid.
I also tried with global older version, 6.6.7 and got the same result.
In my understanding, 6.6.7 was released before the fix above.
So, I'm suspecting that there might be another root cause...
Makoto
On 10/18/2023 2:39 AM, Shigio YAMAGUCHI wrote:
Hello,
I will correct my wrong statement.
The cause seems to be a change in Universal Ctags.
The cause of the problem was not in Universal Ctags, but in my insufficient
bug fixes for the following issues:
Universal Ctags: Don't read config files; New 'ctagsoptfile' configurati
Date: Fri, 07 Apr 2023 13:07:07 +0200
The workaround is still valid.
Regards,
Shigio
On Wed, Oct 18, 2023 at 1:16 PM Shigio YAMAGUCHI <[email protected]> wrote:
Hello,
It found out that Pygments plug-in parser does not work now.
It's not limited to Rust. The cause seems to be a change in
Universal Ctags.
To get it running, do the following:
[/usr/local/share/gtags/script/pygments_parser.py]
142: self.process = subprocess.Popen([ctags_command, '-xu', '--filter', ...
|
v
142: self.process = subprocess.Popen([ctags_command, '-xu',
'--tag-relative=no', '--filter', ...
Harada san, thank you for the report!
Regards,
Shigio
