[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bugs (potential) report for GNU Global

From: ccQ
Subject: Bugs (potential) report for GNU Global
Date: Tue, 21 Apr 2020 20:23:21 -0400

+ What is your environment (OS)?
MacOS Catalina version 10.15.4

+ Which version of GLOBAL are you using?
6.6.4, from homebrew


I am writing a function named `connect-a-and-b` in common lisp. Then use global to generate tags files by `gtags --gtagslabel=pygments`. I use pygments be my lexer, the `~/.globalrc` in my local looks like this one: https://github.com/yoshizow/global-pygments-plugin/blob/master/sample.globalrc

+ What did you do? (command line)
$ global -xs connect
> connect 1 test.lisp (defun connect-a-and-b ()

$ global -xs connect-a-and-b
> #nothing

What did you expect from it?
I expect second command should return result too.

What was occurred? (as is)
At beginning I thought it might be lexer problem of pygments. Then I run its code in my REPL and it lex `connect-a-and-b` correctly. Then I guess it might be global’s issue or problem between pygments call global interface.I have given issue on pygments GitHub.


When I run gtags, it always give me `Warning: ‘{some language}' parser not found. C parser is used instead.`. However, I am pretty sure I write {some language} parser link to pygment correctly in `~/.globalrc`. 

Thank you

reply via email to

[Prev in Thread] Current Thread [Next in Thread]