From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: jaopaulolc@gmail.com, emacs-devel@gnu.org, casouri@gmail.com,
theo@thornhill.no
Subject: Re: Implementation direction for shell-script-mode with tree-sitter
Date: Thu, 27 Oct 2022 09:06:39 +0300 [thread overview]
Message-ID: <83czadn6kw.fsf@gnu.org> (raw)
In-Reply-To: <87tu3q6q8m.fsf@yahoo.com> (message from Po Lu on Thu, 27 Oct 2022 08:54:01 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org, Yuan Fu <casouri@gmail.com>, Theodor Thornhill
> <theo@thornhill.no>, Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 27 Oct 2022 08:54:01 +0800
>
> > My goal is to use the `sh-feature' function to retrieve everything
> > that needs to be fontified for the buffer's shell variant.
>
> So won't you end up, in effect, reproducing the existing font-lock code?
If that's so, I personally am not worried.
From where I stand, the single most important improvement from using
tree-sitter in shell-mode buffers is to solve the problems with
fontifications in tricky cases like here-documents etc. These are a
source of constant stream of bug reports, when people expect us to do
a decent job in those cases. I hope tree-sitter could solve that once
and for all.
next prev parent reply other threads:[~2022-10-27 6:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 15:05 Implementation direction for shell-script-mode with tree-sitter João Paulo Labegalini de Carvalho
2022-10-25 15:46 ` Stefan Monnier
2022-10-25 16:26 ` João Paulo Labegalini de Carvalho
2022-10-26 0:52 ` Po Lu
2022-10-26 15:48 ` João Paulo Labegalini de Carvalho
2022-10-27 0:54 ` Po Lu
2022-10-27 6:06 ` Eli Zaretskii [this message]
2022-10-27 14:23 ` João Paulo Labegalini de Carvalho
2022-10-27 15:53 ` Eli Zaretskii
2022-10-27 14:22 ` João Paulo Labegalini de Carvalho
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=83czadn6kw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jaopaulolc@gmail.com \
--cc=luangruo@yahoo.com \
--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 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.