unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Martin <martin.tang365@googlemail.com>, 70299@debbugs.gnu.org
Subject: bug#70299: 30.0.50; go-ts-mode + tree-sitter-go@v0.20.0 no highlighting
Date: Mon, 8 Apr 2024 22:47:24 -0700	[thread overview]
Message-ID: <09BC30DC-A05E-4FF9-900F-C510C2AC04CE@gmail.com> (raw)
In-Reply-To: <86y19nw1mh.fsf@gnu.org>



> On Apr 8, 2024, at 10:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> Date: Tue, 9 Apr 2024 00:43:57 +0100
>> From:  Martin via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>> 
>> - emacs -Q;
>> - M-x treesit-install-language-grammar
>>  - go
>>  - github.com/tree-sitter/tree-sitter-go
>> 
>> - Open up a new buffer and use go-ts-mode
>> - Write some go-code 
>> ```
>> package my_pkg
>> type myStruct struct {}
>> func MyFunc(x context.Context) error {}
>> ```
>> - Observe that there is no syntax highlighting
>> - Observe that treesit-explore-mode seems to work properly
>> - Conclude that there is something wrong with go-ts-mode's
>>  highlighting. There is highlighting with tree-sitter-go v0.19.1, but
>>  that grammar also seems to come with some bugs.
> 
> Isn't this a duplicate of bug#70296?

Yeah, Martin contacted me on Reddit because he didn’t know how to report this issue, and I told him he can use M-x bug-report-emacs, which he did. Thanks Martin!

Meanwhile I wrote a patch and sent it in bug#70296. Let me merge these two reports.

Yuan




  reply	other threads:[~2024-04-09  5:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 23:43 bug#70299: 30.0.50; go-ts-mode + tree-sitter-go@v0.20.0 no highlighting Martin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09  5:23 ` Eli Zaretskii
2024-04-09  5:47   ` Yuan Fu [this message]
2024-04-09 11:55     ` Martin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 13:08       ` Martin via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-09 23:22         ` Randy Taylor
2024-04-10  8:38           ` Martin via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=09BC30DC-A05E-4FF9-900F-C510C2AC04CE@gmail.com \
    --to=casouri@gmail.com \
    --cc=70299@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=martin.tang365@googlemail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).