From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: On treesit preference for "consumer" modes
Date: Sat, 26 Aug 2023 20:04:10 +0300 [thread overview]
Message-ID: <83il91loqd.fsf@gnu.org> (raw)
In-Reply-To: <7649A9B7-3697-4CA4-BCBE-BAC7DA814B12@gmail.com> (message from JD Smith on Sat, 26 Aug 2023 12:47:18 -0400)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sat, 26 Aug 2023 12:47:18 -0400
>
> The current LANG-mode and LANG-ts-mode separation leaves some ambiguities. One in particular: some modes are “consumers” of other majors modes. That is, they have a different focus, but use LANG modes as subordinate helpers for some aspect of their feature set. Examples: org-mode SRC block highlighting, or a shell mode which wants to highlight and indent code written at the shell prompt. In the pre-treesit era, such a “consumer mode” simply reached for, e.g., LANG-mode for this, directly making use of all the customizations users have applied.
>
> In the new era of LANG-mode and LANG-ts-mode duality, how should the consumer mode decide which one to use?
A user option, I think. There's no other reliable way ATM.
> I guess I’m looking for something like `(treesit-preferred LANG)’ or `(default-major-mode LANG)’.
There's no such thing, and probably won't be, at least not soon enough
for you to rely on it. We are still learning how to deal with this
new situation.
As for your suggestions: treesit-preferred is problematic, because no
one says the user will always prefer ts modes for all of the
languages, nor do we want to force them. As for default-major-mode, I
don't understand how could we implement that, except by deferring to
user options again.
next prev parent reply other threads:[~2023-08-26 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 16:47 On treesit preference for "consumer" modes JD Smith
2023-08-26 17:04 ` Eli Zaretskii [this message]
2023-08-26 17:14 ` Eli Zaretskii
2023-08-26 17:17 ` JD Smith
2023-08-26 17:31 ` Eli Zaretskii
2023-08-26 17:58 ` Eshel Yaron
2023-08-26 19:18 ` JD Smith
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=83il91loqd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jdtsmith@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.