unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Vincenzo Pupillo <v.pupillo@gmail.com>
To: 74610@debbugs.gnu.org, Dmitry Gutov <dmitry@gutov.dev>
Subject: bug#74610: 31.0.50; Submitting mhtml-ts-mode, treesitter alternative to mhtml-mode
Date: Fri, 06 Dec 2024 14:39:56 +0100	[thread overview]
Message-ID: <2157014.9o76ZdvQCi@3-191.divsi.unimi.it> (raw)
In-Reply-To: <97c6e669-b9a2-4e1c-b224-227bb65de0fd@gutov.dev>

Ciao Dmitry,

In data giovedì 5 dicembre 2024 17:51:55 Ora standard dell’Europa centrale, 
Dmitry Gutov ha scritto:
> Hi Vincenzo,
> 
> On 04/12/2024 12:47, Vincenzo Pupillo wrote:
> >> Do you foresee cases for when html-ts-mode would be preferred by the
> >> user instead of this advanced mhtml-ts-mode?
> > 
> > For everyday use mhtml-ts-mode is better, just like mhtml-mode (which has
> > been the default for html editing for a while now).
> > 
> >> Or maybe the former is
> >> better in its current shape when used by e.g. php-ts-mode?
> > 
> > Yes, personally I think that major modes that handle (for tree-sitters)
> > only one language are easier to put together at the moment. It's Lego vs.
> > Playmobil.
> > We are in an experimental phase, like all other editors.
> > See https://github.com/helix-editor/helix/pull/1170#issuecomment-997294090
> > In some ways, by having a different approach from other editors, we have a
> > greater degree of flexibility IMHO.
> 
> Makes sense, thanks.
> 
> >> In other words, I'm wondering why not update the existing mode with
> >> sub-parsers rather than add a new one. html-mode had such a reason -
> >> it's quite old, and has been used in various placed the way it is now
> >> (including multi-mode packages). But ts modes don't work too well with
> >> multi-mode packages, not currently anyway.
> > 
> > It's something I've thought about but haven't tried yet.
> > One of the themes of the email thread (on emacs-devel) was to have a
> > simple
> > multi language major mode that was also a sort of “user's guide.”
> 
> I though the updated html-ts-mode could be that mode. Anyway, good to
> hear that this alternative had been given consideration.

Since the development of Emacs 31 has just started and this major mode is not 
urgent, I will try some experiments in the next few days to see if html-ts-
mode can be modified without compromising the integration with php-ts-mode.

Vincenzo







      reply	other threads:[~2024-12-06 13:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 21:57 bug#74610: 31.0.50; Submitting mhtml-ts-mode, treesitter alternative to mhtml-mode Vincenzo Pupillo
2024-12-01  6:01 ` Yuan Fu
2024-12-01  8:00   ` Eli Zaretskii
2024-12-01  8:18     ` Yuan Fu
2024-12-03 14:29   ` Vincenzo Pupillo
2024-12-11  4:54     ` Yuan Fu
2024-12-04  1:27 ` Dmitry Gutov
2024-12-04 10:47   ` Vincenzo Pupillo
2024-12-05 16:51     ` Dmitry Gutov
2024-12-06 13:39       ` Vincenzo Pupillo [this message]

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=2157014.9o76ZdvQCi@3-191.divsi.unimi.it \
    --to=v.pupillo@gmail.com \
    --cc=74610@debbugs.gnu.org \
    --cc=dmitry@gutov.dev \
    /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).