unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: casouri@gmail.com, emacs-devel@gnu.org,
	mickey@masteringemacs.org, theo@thornhill.no, dgutov@yandex.ru
Subject: Re: Extending define-derived-mode
Date: Thu, 01 Jun 2023 09:39:39 +0300	[thread overview]
Message-ID: <835y87elec.fsf@gnu.org> (raw)
In-Reply-To: <jwvsfbbg7lc.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Thu, 01 Jun 2023 00:06:54 -0400)

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org,
>   mickey@masteringemacs.org,  theo@thornhill.no,  dgutov@yandex.ru
> Date: Thu, 01 Jun 2023 00:06:54 -0400
> 
> > Keep in mind that when people try out tree-sitter modes, they are unlikely
> > to just throw away their config for the old mode; also since tree-sitter and
> > grammars aren’t the easiest to install, people working on multiple machines
> > probably want both tree-sitter and no-tree-sitter modes configured and ready
> > to go. So I think we’ll see a lot of people having config for both modes (me
> > included).
> 
> Good point.

It's a good point, indeed, but with some mode pairs is very hard
(read: impossible) to achieve.  A notable example is c-mode and
c-ts-mode: the former has a lot of mode-specific commands and features
that cannot be used with the latter, because there's no equivalent
infrastructure that supports the same interfaces, and sometimes
because the feature makes no sense in a TS-based mode.  We try very
hard to use the same key bindings and variable names where it does
make sense, but the group of features where that is possible is very
small.  For example, all the enormous set of features we have in CC
mode around indentation and its customization cannot be "ported" to
c-ts-mode and c++-ts-mode, because the latter is built on completely
different analysis of the text.  Another example is the ad-hoc support
for some frequently-use macro names that CC mode has.



  reply	other threads:[~2023-06-01  6:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30  5:16 Extending define-derived-mode Yuan Fu
2023-05-30  5:51 ` Theodor Thornhill
2023-05-31 20:35   ` Yuan Fu
2023-06-01  5:43     ` Theodor Thornhill
2023-05-30 10:48 ` Eli Zaretskii
2023-05-30 14:16   ` Stefan Monnier
2023-05-31 21:31     ` Yuan Fu
2023-06-01  4:06       ` Stefan Monnier
2023-06-01  6:39         ` Eli Zaretskii [this message]
2023-06-02  7:50           ` Yuan Fu
2023-06-02 11:54             ` Eli Zaretskii
2023-06-05  7:31               ` Yuan Fu
2023-06-05 11:33                 ` Eli Zaretskii
2023-06-08  7:25                   ` Yuan Fu
2023-06-02  7:44         ` Yuan Fu
2023-06-02 16:46           ` Stefan Monnier
2023-06-05  7:39             ` Yuan Fu
2023-06-05 15:17               ` Stefan Monnier
2023-05-31 20:48   ` Yuan Fu
2023-06-01  5:47     ` Eli Zaretskii
2023-06-02  7:45       ` Yuan Fu
2023-06-02 11:51         ` Eli Zaretskii
2023-05-30 17:24 ` Juri Linkov
2023-06-05  8:30 ` Philip Kaludercic

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=835y87elec.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=casouri@gmail.com \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=mickey@masteringemacs.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).