From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gernotk@gmail.com, emacs-devel@gnu.org
Subject: Re: Treesit says grammar is unavailable when it
Date: Tue, 26 Dec 2023 22:41:23 -0800 [thread overview]
Message-ID: <D2B66BBE-E8D6-431A-AF77-76A57C37D23A@gmail.com> (raw)
In-Reply-To: <83y1dtjkkf.fsf@gnu.org>
> On Dec 17, 2023, at 12:32 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 16 Dec 2023 22:31:02 -0800
>> Cc: gernotk@gmail.com,
>> emacs-devel@gnu.org
>>
>>> On Dec 14, 2023, at 12:27 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>
>>>> We were showing error messages from dlopen, and then removed them for brevity, see e8df6c311fcf59bf23d31b9db2bb8fec9d78fbe7
>>>
>>> If these messages are useful, we can revert that commit.
>>
>> I forgot to ask, should this be on emacs-29 or master?
>
> On master, I think.
>
>>>> Maybe we can fold the extra error messages by default?
>>>
>>> I'm not sure I understand the details, but the idea is certainly okay.
>>
>> I’m thinking about applying text property to the extra messages so they appear as “…”, and is expanded when clicked (or hit enter), like what we have for printing large objects in the scratch buffer.
>
> Sounds like over-engineering to me. I don't think we do anything like
> that in any other case where we emit error messages?
Yeah, I might be overthinking this. Reverted on master.
Yuan
next prev parent reply other threads:[~2023-12-27 6:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 12:43 Treesit says grammar is unavailable when it Gernot Kieseritzky
2023-12-13 3:33 ` Yuan Fu
2023-12-13 12:00 ` Eli Zaretskii
2023-12-14 8:14 ` Yuan Fu
2023-12-14 8:27 ` Eli Zaretskii
2023-12-15 2:43 ` Madhu
2023-12-15 9:00 ` Eli Zaretskii
2023-12-17 6:31 ` Yuan Fu
2023-12-17 8:32 ` Eli Zaretskii
2023-12-27 6:41 ` Yuan Fu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-10 9:24 mprodrigues
2023-03-10 12:32 ` 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=D2B66BBE-E8D6-431A-AF77-76A57C37D23A@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gernotk@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).