From: Eli Zaretskii <eliz@gnu.org>
To: Gregory Heytings <gregory@heytings.org>
Cc: 57212@debbugs.gnu.org, dick.r.chiang@gmail.com
Subject: bug#57212: 29.0.50; [PATCH] Citizen's arrest of end-of-defun-moves-to-eol
Date: Tue, 16 Aug 2022 05:29:59 +0300 [thread overview]
Message-ID: <83czd0hqe0.fsf@gnu.org> (raw)
In-Reply-To: <3a1232a17bcbf1cba5cc@heytings.org> (message from Gregory Heytings on Mon, 15 Aug 2022 19:44:32 +0000)
> Cc: 57212@debbugs.gnu.org
> Date: Mon, 15 Aug 2022 19:44:32 +0000
> From: Gregory Heytings <gregory@heytings.org>
>
> > If you're convinced narrowing within a critical section of redisplay is
> > safe (and I suspect it is), do it all the time, not just when
> > "long_line_optimizations_p" is true.
>
> That might indeed be what Emacs could do in the long term, once we have
> enough experience with it.
No, it shouldn't, because of the adverse effects of that on some
aspects of the Emacs behavior.
next prev parent reply other threads:[~2022-08-16 2:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 18:02 bug#57212: 29.0.50; [PATCH] Citizen's arrest of end-of-defun-moves-to-eol dick.r.chiang
2022-08-14 18:39 ` Eli Zaretskii
2022-08-14 20:49 ` dick
2022-08-15 7:06 ` Lars Ingebrigtsen
2022-08-15 19:44 ` Gregory Heytings
2022-08-16 2:29 ` Eli Zaretskii [this message]
2022-08-16 8:14 ` Gregory Heytings
2022-08-16 12:59 ` 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=83czd0hqe0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57212@debbugs.gnu.org \
--cc=dick.r.chiang@gmail.com \
--cc=gregory@heytings.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).