From: Yuan Fu <casouri@gmail.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 64830@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>,
Eli Zaretskii <eliz@gnu.org>
Subject: bug#64830: 30.0.50 C++ treesitter mode no coloration
Date: Mon, 26 Aug 2024 18:58:13 -0700 [thread overview]
Message-ID: <78DD1528-A12B-4199-9822-157852080027@gmail.com> (raw)
In-Reply-To: <CADwFkmn22u8fLZE-zLBm+NmbhDVnfBgbeDzZitWOi5hXF01AGA@mail.gmail.com>
> On Aug 26, 2024, at 3:25 PM, Stefan Kangas <stefankangas@gmail.com> wrote:
>
> Alan Mackenzie <acm@muc.de> writes:
>
>> How about outputting a message looking something like this:
>>
>> Loading /home/acm/.emacs.d/tree-sitter/libtree-sitter.so ....Done
>>
>> .. This wouldn't get in the way, yet might well prevent some of the
>> problems I've been having over the last few days.
>
> Makes sense to me, FWIW. Perhaps we should have a knob to
> enable/disable such messages though.
>
> I'm also not sure what should be the default. Perhaps we should
> experiment with it and take a final decision when we have some
> experience with using it.
Yeah, that’ll be a very useful feature. To determining which grammar my Emacs instance loaded, I had to delete the object file and see if Emacs complains it can’t find any grammar. I think it’s fine to print this to message buffer by default, it’ll only happen once and we already do such things for loading a elisp file.
I searched a bit and it seems ldaddr can find the location of a loaded shared library. Doesn’t seem hard to implement.
I also want a lisp function that can return the location of a loaded grammar file, would that be an overkill if we have the aforementioned printing?
Yuan
next prev parent reply other threads:[~2024-08-27 1:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 9:13 bug#64830: 29.1; C++ treesitter mode no coloration David Come
2023-07-24 12:32 ` Eli Zaretskii
2024-08-14 17:35 ` bug#64830: 30.0.50 " Alan Mackenzie
2024-08-15 5:25 ` Eli Zaretskii
2024-08-16 16:44 ` Alan Mackenzie
2024-08-16 17:40 ` Eli Zaretskii
2024-08-16 17:45 ` Eli Zaretskii
2024-08-16 18:06 ` Alan Mackenzie
2024-08-16 18:27 ` Eli Zaretskii
2024-08-20 3:46 ` Yuan Fu
2024-08-24 18:35 ` Yuan Fu
2024-08-24 19:38 ` Alan Mackenzie
2024-08-24 20:43 ` Yuan Fu
2024-08-25 2:19 ` Alan Mackenzie
2024-08-25 4:54 ` Eli Zaretskii
2024-08-25 12:08 ` Alan Mackenzie
2024-08-25 12:17 ` Eli Zaretskii
2024-08-25 22:40 ` Yuan Fu
2024-08-26 17:25 ` Alan Mackenzie
2024-08-26 17:51 ` Eli Zaretskii
2024-08-26 19:50 ` Alan Mackenzie
2024-08-26 22:25 ` Stefan Kangas
2024-08-27 1:58 ` Yuan Fu [this message]
2024-08-27 12:09 ` Eli Zaretskii
2024-08-28 5:36 ` Yuan Fu
2024-08-28 12:33 ` Eli Zaretskii
2024-08-29 4:54 ` Yuan Fu
2024-08-29 6:01 ` Eli Zaretskii
2024-09-11 5:09 ` Yuan Fu
2024-09-11 12:09 ` Eli Zaretskii
2024-09-12 8:06 ` Yuan Fu
2024-08-27 12:01 ` Eli Zaretskii
2024-08-27 11:03 ` Eli Zaretskii
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=78DD1528-A12B-4199-9822-157852080027@gmail.com \
--to=casouri@gmail.com \
--cc=64830@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=eliz@gnu.org \
--cc=stefankangas@gmail.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).