From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>, dancol@dancol.org
Cc: emacs-devel@gnu.org
Subject: Re: c-ts-mode style customization
Date: Fri, 24 Mar 2023 09:19:53 +0300 [thread overview]
Message-ID: <83o7oiekmu.fsf@gnu.org> (raw)
In-Reply-To: <FC9F4094-DDA6-4281-8AC8-34B4D4D3BB79@gmail.com> (message from Yuan Fu on Thu, 23 Mar 2023 16:44:31 -0700)
> From: Yuan Fu <casouri@gmail.com>
> Date: Thu, 23 Mar 2023 16:44:31 -0700
> Cc: emacs-devel@gnu.org
>
> >> Anyway, I agree with the general idea. I’ll add the option to set a rule alist.
> >
> >
> > I gave you a concrete example of a disadvantage of using functions that return data over just using plain data. The principle of least power applies here.
>
> Still, it’s largely harmless, and could prove useful for some people, also it’s too late to remove it from emacs-29. And since it’s in emacs-29, I don’t want to go through the trouble removing it in emacs-30 in a backward-compatible way.
While all this is true, the question is how bad the problem is.
Daniel says the TS modes are unusable for him due to this issue.
Daniel, could you please post a recipe, starting from "emacs -Q", to
reproduce the "blinking" during editing you described up-thread?
Preferably while editing some code that one can meet reasonably
frequently in practice. I'd like to play with the example and see
whether the problem is serious enough for us to try to solve it ASAP.
TIA.
next prev parent reply other threads:[~2023-03-24 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 15:53 c-ts-mode style customization Daniel Colascione
2023-03-22 16:48 ` Eli Zaretskii
2023-03-22 23:58 ` Yuan Fu
2023-03-23 0:05 ` Daniel Colascione
2023-03-23 0:20 ` Yuan Fu
2023-03-23 4:55 ` Daniel Colascione
2023-03-23 19:20 ` Yuan Fu
2023-03-23 21:06 ` Daniel Colascione
2023-03-23 23:44 ` Yuan Fu
2023-03-24 6:19 ` Eli Zaretskii [this message]
2023-03-24 7:02 ` Yuan Fu
2023-03-24 11:37 ` Eli Zaretskii
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=83o7oiekmu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
/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).