From: Eli Zaretskii <eliz@gnu.org>
To: Noah Peart <noah.v.peart@gmail.com>
Cc: 70361@debbugs.gnu.org, casouri@gmail.com
Subject: bug#70361: [PATCH] Add font-locking for operators in go-ts-mode.
Date: Sat, 13 Apr 2024 12:33:15 +0300 [thread overview]
Message-ID: <86sezpppyc.fsf@gnu.org> (raw)
In-Reply-To: <CAPVBTSccb5e=pU1c9YSgoh828Wy5ey7zpzR80MSMxpL+GSRGrQ@mail.gmail.com> (message from Noah Peart on Sat, 13 Apr 2024 00:53:45 -0700)
> From: Noah Peart <noah.v.peart@gmail.com>
> Date: Sat, 13 Apr 2024 00:53:45 -0700
> Cc: Yuan Fu <casouri@gmail.com>, 70361@debbugs.gnu.org
>
> > What problems do you see with the current approach that would require
> more fine-grained user control?
>
> The main issue for me is removing the `error` feature from any mode
> that adds it with `:override t`. I find the override font-locking is jarring - in some
> Languages half the buffer can switch in and out of parse errors when you
> do something as simple as removing a closing paren.
Maybe we should have a user option to turn error feature on and off.
Yuan, WDYT?
> Also, allowing users to rearrange features at different levels seems like a bonus.
Not sure about this one. We didn't have that in the traditional
font-lock, did we?
next prev parent reply other threads:[~2024-04-13 9:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-13 5:23 bug#70361: [PATCH] Add font-locking for operators in go-ts-mode Noah Peart
2024-04-13 7:20 ` Eli Zaretskii
2024-04-13 7:27 ` Noah Peart
2024-04-13 7:32 ` Noah Peart
2024-04-13 7:40 ` Eli Zaretskii
2024-04-13 7:53 ` Noah Peart
2024-04-13 9:33 ` Eli Zaretskii [this message]
2024-04-14 23:25 ` Yuan Fu
2024-04-14 23:34 ` Yuan Fu
2024-04-15 12:05 ` Noah Peart
2024-04-16 1:49 ` Randy Taylor
2024-04-16 5:57 ` Yuan Fu
2024-04-16 5:58 ` Yuan Fu
2024-04-16 12:34 ` Eli Zaretskii
2024-04-17 2:47 ` Yuan Fu
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=86sezpppyc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70361@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=noah.v.peart@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.