From: Yuan Fu <casouri@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Need for "-ts-mode" modes
Date: Thu, 29 Dec 2022 11:27:41 -0800 [thread overview]
Message-ID: <279658FD-ABF9-4127-A646-038C60A79EA1@gmail.com> (raw)
In-Reply-To: <87mt76f4n4.fsf@posteo.net>
>
>>> or creating new modes that depend
>>> on tree-sitter and that don't work or even try to provide some fall-back
>>> if the library is not available.
>>
>> I fail to see what's wrong with that. It is entirely legitimate to
>> have a major mode which depends on an optional feature and doesn't
>> work without it.
>
> Naturally, if there is no way around this. My argument is that there
> is. What prompted me to ask this question was when I just opened a
> Dockerfile and a warning popped up, telling me that I was missing the
> right libraries.
I think we should not enable docker-ts-mode in auto-mode-alist if (treesit-language-available-p 'dockerfile) is nil. This way you don’t get the warning. In Emacs 30 we can upgrade the auto-mode facility to use different modes based on some condition.
Yuan
next prev parent reply other threads:[~2022-12-29 19:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 17:08 Need for "-ts-mode" modes Philip Kaludercic
2022-12-29 17:42 ` Eli Zaretskii
2022-12-29 18:26 ` Philip Kaludercic
2022-12-29 19:27 ` Yuan Fu [this message]
2022-12-29 19:42 ` Eli Zaretskii
2022-12-30 4:05 ` Richard Stallman
2022-12-30 8:49 ` Eli Zaretskii
2022-12-29 19:57 ` Eli Zaretskii
2022-12-29 20:23 ` Eli Zaretskii
2022-12-30 10:58 ` Unifying "foo-mode"s and "foo-ts-mode"s Philip Kaludercic
2022-12-30 12:50 ` Theodor Thornhill
2022-12-30 13:08 ` Philip Kaludercic
2022-12-30 13:19 ` Theodor Thornhill
2022-12-30 15:02 ` Philip Kaludercic
2022-12-30 15:24 ` Theodor Thornhill
2022-12-30 15:45 ` Philip Kaludercic
2022-12-30 15:42 ` Eli Zaretskii
2022-12-30 15:57 ` Philip Kaludercic
2022-12-30 16:20 ` Eli Zaretskii
2022-12-30 16:39 ` Philip Kaludercic
2022-12-30 17:05 ` Eli Zaretskii
2022-12-31 0:13 ` Philip Kaludercic
2022-12-31 6:38 ` Eli Zaretskii
2022-12-30 15:02 ` Eli Zaretskii
2022-12-30 15:20 ` Philip Kaludercic
2022-12-30 15:52 ` Eli Zaretskii
2022-12-30 16:09 ` Philip Kaludercic
2022-12-30 16:30 ` Stefan Monnier
2022-12-30 17:03 ` Eli Zaretskii
2023-01-01 3:03 ` Richard Stallman
2023-01-01 7:28 ` Eli Zaretskii
2023-01-03 4:07 ` Richard Stallman
2023-01-03 12:11 ` Eli Zaretskii
2023-01-05 3:34 ` Richard Stallman
2022-12-30 17:10 ` Gregory Heytings
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=279658FD-ABF9-4127-A646-038C60A79EA1@gmail.com \
--to=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
/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).