From: Philip Kaludercic <philipk@posteo.net>
To: Gregory Heytings <gregory@heytings.org>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: feature/fix-the-long-lines-display-bug c760d2ed16: * etc/PROBLEMS: Remove the entry which is no longer relevant.
Date: Tue, 19 Jul 2022 04:10:41 +0000 [thread overview]
Message-ID: <87tu7dwxmm.fsf@posteo.net> (raw)
In-Reply-To: <fa7b8ced351ccfbfe07c@heytings.org> (Gregory Heytings's message of "Mon, 18 Jul 2022 21:46:53 +0000")
Gregory Heytings <gregory@heytings.org> writes:
>>
>> I just tried it out, and while it certainly is an improvement, I
>> noticed that the performance appears to depend on the direction the
>> point moves. E.g. I generated a long line using
>>
>> yes abbbbbbbbbbbbbbbbbbbb | head -100000 | tr -d '\n' > long-line
>>
>> and I could C-v to the end without any issues. But M-v was
>> significantly slower. The same applies to C-f vs. C-b.
>>
>
> Yes, the same is true without long lines, moving backward is slower
> than moving forward (but you probably meant C-p vs C-n, not C-f vs
> C-b).
No, I meant C-f and C-b, as the file contained only one line, but the
same applies to C-p and C-n.
next prev parent reply other threads:[~2022-07-19 4:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165817030092.24067.4562191765367761985@vcs2.savannah.gnu.org>
[not found] ` <20220718185141.39F11C0F203@vcs2.savannah.gnu.org>
2022-07-18 21:01 ` feature/fix-the-long-lines-display-bug c760d2ed16: * etc/PROBLEMS: Remove the entry which is no longer relevant Stefan Monnier
2022-07-18 21:04 ` Gregory Heytings
2022-07-18 21:36 ` Philip Kaludercic
2022-07-18 21:46 ` Gregory Heytings
2022-07-19 4:10 ` Philip Kaludercic [this message]
2022-07-19 5:21 ` Gregory Heytings
2022-07-21 11:50 ` Gregory Heytings
2022-07-21 12:43 ` Stefan Kangas
2022-07-21 14:51 ` Daniel Martín
2022-07-21 15:25 ` Stefan Monnier
2022-07-21 16:09 ` Eli Zaretskii
2022-07-21 16:36 ` Gregory Heytings
2022-07-22 14:48 ` Lars Ingebrigtsen
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=87tu7dwxmm.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=monnier@iro.umontreal.ca \
/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).