From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: johan.myreen@gmail.com, emacs-devel@gnu.org
Subject: Re: An anonymous IRC user's opinion
Date: Sun, 13 Oct 2024 07:41:34 +0300 [thread overview]
Message-ID: <86cyk4vcld.fsf@gnu.org> (raw)
In-Reply-To: <9a8b97f8-def3-43ce-b71b-1f09bb05afd4@gutov.dev> (message from Dmitry Gutov on Sat, 12 Oct 2024 23:27:01 +0300)
> Date: Sat, 12 Oct 2024 23:27:01 +0300
> Cc: johan.myreen@gmail.com, emacs-devel@gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> > Feel free to improve what we have. My point is that it is not very
> > trivial; what we have is basically a compromise, which could be
> > improved, at least for some languages, if we want to be smarter.
>
> The proposal I'm quoting is straightforward: if Emacs is compiled with
> tree-sitter support, enable the modes and warn when the grammars are not
> available. If Emacs is not compiled with tree-sitter, do neither.
>
> That kind of rule has predictability: for example if the grammar was not
> installed originally but the user did that while Emacs was running, the
> corresponding major mode will start working the next time the user tries
> to enable it. That wouldn't be the case if we conditionally alter
> auto-mode-alist based on grammar availability.
>
> The above approach should be quite easy to implement, if there's
> agreement to it. Otherwise, the issue is about choosing the details of
> the UI first.
It is not clear which modes you suggest that should behave like that.
Surely, not all of them, i.e. including those for which non-TS modes
are part of Emacs?
And yes, I would like to hear from more people what they think about
the possible behaviors in these cases, including how to handle missing
grammar libraries.
next prev parent reply other threads:[~2024-10-13 4:41 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-06 7:32 An anonymous IRC user's opinion Abraham S.A.H. via Emacs development discussions.
2024-10-06 8:10 ` Emanuel Berg
2024-10-06 8:44 ` Dr. Arne Babenhauserheide
2024-10-06 9:01 ` Emanuel Berg
2024-10-06 9:09 ` Emanuel Berg
2024-10-06 9:32 ` Abraham S.A.H. via Emacs development discussions.
2024-10-06 11:28 ` Dr. Arne Babenhauserheide
2024-10-06 13:10 ` Emanuel Berg
2024-10-06 12:55 ` Emanuel Berg
2024-10-09 3:29 ` Richard Stallman
2024-10-09 20:20 ` Emanuel Berg
2024-10-10 8:57 ` Dr. Arne Babenhauserheide
2024-10-09 3:30 ` Richard Stallman
2024-10-09 6:48 ` Dr. Arne Babenhauserheide
2024-10-09 20:22 ` Emanuel Berg
2024-10-09 11:09 ` Johan Myréen
2024-10-09 13:13 ` Eli Zaretskii
2024-10-09 13:38 ` tomas
2024-10-09 16:02 ` Dr. Arne Babenhauserheide
2024-10-09 16:22 ` Eli Zaretskii
2024-10-09 21:55 ` Emanuel Berg
2024-10-10 7:25 ` Eli Zaretskii
2024-10-10 9:35 ` Dr. Arne Babenhauserheide
2024-10-10 10:42 ` Eli Zaretskii
2024-10-13 3:29 ` Richard Stallman
2024-10-10 6:07 ` Emanuel Berg
2024-10-09 16:06 ` Johan Myréen
2024-10-09 16:12 ` Ship Mints
2024-10-09 16:25 ` Eli Zaretskii
2024-10-09 21:25 ` Dmitry Gutov
2024-10-10 4:56 ` Eli Zaretskii
2024-10-10 5:14 ` Xiyue Deng
2024-10-10 6:36 ` Eli Zaretskii
2024-10-10 6:59 ` Xiyue Deng
2024-10-11 20:30 ` Dmitry Gutov
2024-10-12 7:34 ` Eli Zaretskii
2024-10-12 20:27 ` Dmitry Gutov
2024-10-12 21:00 ` Dr. Arne Babenhauserheide
2024-10-13 4:53 ` Eli Zaretskii
2024-10-13 6:28 ` Dr. Arne Babenhauserheide
2024-10-13 4:41 ` Eli Zaretskii [this message]
2024-10-13 9:37 ` Dmitry Gutov
2024-10-13 10:39 ` Eli Zaretskii
2024-10-13 15:31 ` Dmitry Gutov
2024-10-13 15:53 ` Eli Zaretskii
2024-10-14 9:32 ` Dmitry Gutov
2024-10-14 11:09 ` Alan Mackenzie
2024-10-15 1:41 ` Dmitry Gutov
2024-10-14 14:16 ` Eli Zaretskii
2024-10-15 1:36 ` Dmitry Gutov
2024-10-15 12:03 ` Eli Zaretskii
2024-10-13 10:52 ` Dr. Arne Babenhauserheide
2024-10-10 13:58 ` Richard Stallman
2024-10-10 14:45 ` Dr. Arne Babenhauserheide
2024-10-12 3:19 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2024-10-06 5:31 Pedro Andres Aranda Gutierrez
2024-10-06 6:04 ` Emanuel Berg
2024-10-06 9:06 ` Dr. Arne Babenhauserheide
2024-10-06 9:10 ` Emanuel Berg
2024-10-06 10:31 ` Pedro Andres Aranda Gutierrez
2024-10-07 21:17 ` John ff
2024-10-13 3:29 ` Richard Stallman
2024-10-01 20:09 Jordi Gutiérrez Hermoso
2024-10-04 16:25 ` Eduardo Ochs
2024-10-04 18:10 ` Dr. Arne Babenhauserheide
2024-10-04 18:30 ` Eduardo Ochs
2024-10-04 19:24 ` Dr. Arne Babenhauserheide
2024-10-04 20:37 ` Eduardo Ochs
2024-10-05 8:41 ` Dr. Arne Babenhauserheide
2024-10-05 12:57 ` Eduardo Ochs
2024-10-05 13:21 ` Emanuel Berg
2024-10-05 15:57 ` Dr. Arne Babenhauserheide
2024-10-09 3:30 ` Richard Stallman
2024-10-09 7:04 ` Eduardo Ochs
2024-10-07 3:54 ` Richard Stallman
2024-10-07 4:14 ` Emanuel Berg
2024-10-07 14:27 ` Ship Mints
2024-10-07 14:46 ` Emanuel Berg
2024-10-07 10:31 ` Dr. Arne Babenhauserheide
2024-10-10 0:22 ` chad
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cyk4vcld.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dmitry@gutov.dev \
--cc=emacs-devel@gnu.org \
--cc=johan.myreen@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.