From: Eli Zaretskii <eliz@gnu.org>
To: Theodor Thornhill <theo@thornhill.no>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca
Subject: Re: master 09b5f00613: ; Fix calls to treesit functions
Date: Mon, 19 Dec 2022 14:29:45 +0200 [thread overview]
Message-ID: <83sfhbefuu.fsf@gnu.org> (raw)
In-Reply-To: <A7F8E892-3492-4B77-B5FB-4EB3ABD90A20@thornhill.no> (message from Theodor Thornhill on Mon, 19 Dec 2022 07:26:35 +0100)
> Date: Mon, 19 Dec 2022 07:26:35 +0100
> From: Theodor Thornhill <theo@thornhill.no>
>
> How about treesit-ensure, that checks treesit-available-p and whether it's enabled for the current mode? The treesit-parser-list is also kind of working just by accident, as it isn't its job to ensure availability.
Isn't that what treesit-language-available-p already does?
next prev parent reply other threads:[~2022-12-19 12:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <167138365421.15060.2886694741391315956@vcs2.savannah.gnu.org>
[not found] ` <20221218171414.77B8EC0060F@vcs2.savannah.gnu.org>
2022-12-18 20:19 ` master 09b5f00613: ; Fix calls to treesit functions Stefan Monnier
2022-12-18 23:02 ` Yuan Fu
2022-12-18 23:54 ` Stefan Monnier
2022-12-19 8:26 ` Yuan Fu
2022-12-19 3:23 ` Eli Zaretskii
2022-12-19 3:37 ` Stefan Monnier
2022-12-19 6:26 ` Theodor Thornhill
2022-12-19 8:35 ` Yuan Fu
2022-12-19 9:07 ` Theodor Thornhill
2022-12-19 12:29 ` Eli Zaretskii [this message]
2022-12-19 13:47 ` Theodor Thornhill
2022-12-19 14:40 ` Eli Zaretskii
2022-12-19 14:51 ` Theodor Thornhill
2022-12-19 15:21 ` Eli Zaretskii
2022-12-19 15:44 ` Dmitry Gutov
2022-12-19 16:42 ` Theodor Thornhill
2022-12-19 16:57 ` Eli Zaretskii
2022-12-19 16:13 ` Stefan Monnier
2022-12-19 16:42 ` Theodor Thornhill
2022-12-20 0:12 ` Yuan Fu
2022-12-20 3:39 ` Eli Zaretskii
2022-12-20 4:37 ` Stefan Monnier
2022-12-20 13:59 ` Eli Zaretskii
2022-12-20 15:35 ` Stefan Monnier
2022-12-20 15:44 ` Eli Zaretskii
2022-12-20 16:02 ` Stefan Monnier
2022-12-21 0:36 ` Yuan Fu
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=83sfhbefuu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=theo@thornhill.no \
/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).