From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 63750@debbugs.gnu.org, Mickey Petersen <mickey@masteringemacs.org>
Subject: bug#63750: 30.0.50; tree-sitter: `treesit-language-source-alist' is not customisable
Date: Mon, 29 May 2023 13:37:06 -0700 [thread overview]
Message-ID: <E8EB93F9-AC2F-4FA6-85A5-63153FD3C21F@gmail.com> (raw)
In-Reply-To: <83cz2jgq05.fsf@gnu.org>
> On May 29, 2023, at 7:40 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sun, 28 May 2023 15:51:05 -0700
>> Cc: mickey@masteringemacs.org,
>> 63750@debbugs.gnu.org
>>
>>
>>
>>> On May 27, 2023, at 10:32 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>
>>>> From: Yuan Fu <casouri@gmail.com>
>>>> Date: Sat, 27 May 2023 16:12:18 -0700
>>>> Cc: Mickey Petersen <mickey@masteringemacs.org>,
>>>> 63750@debbugs.gnu.org
>>>>
>>>>> However, I think we decided to make it so that each installation
>>>>> should update the value of the variable with the data of the grammar
>>>>> just installed. I see that we don't actually do that -- Yuan, am I
>>>>> misremembering this? If not, would you please add code to add to the
>>>>> variable's value the data of every grammar that is installed?
>>>>
>>>> Sure. Does it need to be preserved across sessions (ie, use custom)? Or just add for the current session?
>>>
>>> Only for the current session. Users who want it preserved should do
>>> it themselves (I will add that to the doc string when the code which
>>> updates the variable is installed).
>>
>> Done.
>
> Thanks. And I see that you have updated the doc string accordingly.
Glad my docstring worked out this time ;-)
Yuan
prev parent reply other threads:[~2023-05-29 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-27 12:01 bug#63750: 30.0.50; tree-sitter: `treesit-language-source-alist' is not customisable Mickey Petersen
2023-05-27 12:32 ` Eli Zaretskii
2023-05-27 23:12 ` Yuan Fu
2023-05-28 5:32 ` Eli Zaretskii
2023-05-28 22:51 ` Yuan Fu
2023-05-29 14:40 ` Eli Zaretskii
2023-05-29 20:37 ` Yuan Fu [this message]
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=E8EB93F9-AC2F-4FA6-85A5-63153FD3C21F@gmail.com \
--to=casouri@gmail.com \
--cc=63750@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mickey@masteringemacs.org \
/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).