[Top][All Lists]

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

Re: Bugs (potential) report for GNU Global

From: Shigio YAMAGUCHI
Subject: Re: Bugs (potential) report for GNU Global
Date: Wed, 22 Apr 2020 10:11:13 +0900

Could you please give me a reproduce method to understand the problem?


2020年4月22日(水) 10:05 ccQ <address@hidden>:
> + What is your environment (OS)?
> MacOS Catalina version 10.15.4
> + Which version of GLOBAL are you using?
> 6.6.4, from homebrew
> **First:**
> 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.
> **Second:**
> 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`.
> Best,
> Thank you

Shigio YAMAGUCHI <address@hidden>
PGP fingerprint:
26F6 31B4 3D62 4A92 7E6F  1C33 969C 3BE3 89DD A6EB

reply via email to

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