From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 29889@debbugs.gnu.org
Subject: bug#29889: 27.0.50; Slow visual selection
Date: Sat, 21 May 2022 20:24:23 +0800 [thread overview]
Message-ID: <871qwnt6o8.fsf@yahoo.com> (raw)
In-Reply-To: <87bkvrytan.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 21 May 2022 14:16:48 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Yes, that should work. And there probably aren't that many of these
> commands, so it should be possible to get them all marked with
> reasonable confidence.
But what if some other command moves the region? For example, if you
type "C-x h" and then "C-f"?
The selection should also be updated then, I think, to match the text
displayed in the region face. The best way to solve the performance
problem is probably to fall back to using buffer positions instead of
strings if the region exceeds a certain amount of characters in length.
next prev parent reply other threads:[~2022-05-21 12:24 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 3:52 bug#29889: 27.0.50; Slow visual selection Sujith
2017-12-29 9:04 ` Eli Zaretskii
2017-12-30 1:36 ` Sujith
2017-12-30 10:23 ` Eli Zaretskii
2017-12-31 5:25 ` Sujith
2017-12-31 7:20 ` Eli Zaretskii
2017-12-31 7:29 ` Eli Zaretskii
2018-01-06 1:15 ` Sujith
2018-01-06 8:37 ` Eli Zaretskii
2018-01-06 15:37 ` Stefan Monnier
2018-01-06 16:16 ` Eli Zaretskii
2018-01-07 15:24 ` bug#29889: [SUSPECTED SPAM] " Stefan Monnier
2018-01-07 16:08 ` martin rudalics
2018-01-07 17:36 ` Eli Zaretskii
2018-01-07 17:54 ` Stefan Monnier
2018-01-06 15:46 ` Sujith
2017-12-31 8:42 ` Sujith
2017-12-31 15:37 ` Eli Zaretskii
2017-12-31 18:43 ` Eli Zaretskii
2022-04-21 13:25 ` Lars Ingebrigtsen
2022-05-20 2:13 ` Lars Ingebrigtsen
2022-05-20 7:16 ` Eli Zaretskii
2022-05-20 9:07 ` Lars Ingebrigtsen
2022-05-20 8:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 8:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 11:02 ` Eli Zaretskii
2022-05-20 9:03 ` Lars Ingebrigtsen
2022-05-20 9:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 10:11 ` Lars Ingebrigtsen
2022-05-20 11:13 ` Eli Zaretskii
2022-05-20 11:32 ` Lars Ingebrigtsen
2022-05-20 11:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 12:13 ` Eli Zaretskii
2022-05-20 12:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 12:21 ` Eli Zaretskii
2022-05-20 12:47 ` Lars Ingebrigtsen
2022-05-20 13:19 ` Eli Zaretskii
2022-05-21 12:16 ` Lars Ingebrigtsen
2022-05-21 12:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-21 13:29 ` Lars Ingebrigtsen
2022-05-22 1:13 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-22 11:16 ` Lars Ingebrigtsen
2022-05-22 12:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-22 12:11 ` Lars Ingebrigtsen
2022-05-22 12:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 7:50 ` Lars Ingebrigtsen
2022-05-23 9:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-23 9:11 ` Lars Ingebrigtsen
2022-05-23 9:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 11:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 11:52 ` Lars Ingebrigtsen
2022-05-20 11:08 ` Eli Zaretskii
2022-05-20 11:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 12:19 ` Eli Zaretskii
2022-05-20 12:39 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 13:18 ` Eli Zaretskii
2022-05-20 13:27 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 11:03 ` Eli Zaretskii
2022-05-20 11:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-20 12:16 ` 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=871qwnt6o8.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=29889@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.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 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).