From: James McClain <jamezmcclain@gmail.com>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 23457@debbugs.gnu.org
Subject: bug#23457: 24.5; interactive use of next-line and previous-line (holding down C-n or C-p) lag in a buffer with all spaces and newlines
Date: Fri, 6 May 2016 01:43:55 -0700 [thread overview]
Message-ID: <CAEsaJvPTBHbrdnmwUvO27A0PAgXN90MZKthKMuAk-_7+nWNgzg@mail.gmail.com> (raw)
In-Reply-To: <87h9ebr50n.fsf@petton.fr>
The linux box has nothing in common with my windows box, there should
be no configurations shared that effect emacs, especially since I run
it with -Q.
For this to happen there needs to be many lines of just spaces and a
newline. I talked about in a previous message having 67 of those
lines, but I believe on my linux box it required more (less than 100
though). You also need to go to the very end of the file M->, then
scroll up through the lines up to the top. I did not make that clear.
Here is another take on the recipe, hopefully I can clear up any confusion.
This is without resizing the window, so window-body-width should be 80.
1. .\emacs-25.0.93.exe -Q
2. C-x b test-2 <ret>
3. <f3>
4. C-u 80 <space>
5. C-j
6. <f4>
7. C-u 120 <f4>
8. You should now be at the bottom of the buffer and at the first column,
but it doesn't hurt to hit M-> and C-a, so do that.
9. Now try moving up to the top of the buffer with C-p
I experience lag doing this, to be clear about what I mean by that. I
can cancel by using C-g, but unless I do that, I cannot execute
commands until emacs finishes moving up lines. Which takes much longer
than if instead of all spaces, I had instead one period before the
newline.
I cannot remember if I tested with with emacs -Q -nw on linux. I will
report on this tomorrow as well as test the windows build on a newly
deployed computer and maybe test it in a virtual box VM. I may also
try setting it up tonight if I have the energy.
On Fri, May 6, 2016 at 12:59 AM, Nicolas Petton <nicolas@petton.fr> wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> I believe you. I just cannot reproduce this on any machine to which I
>> have access.
>
> I also can't reproduce it on my Linux box with Emacs 25.0.93.
>
> Nico
next prev parent reply other threads:[~2016-05-06 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 9:01 bug#23457: 24.5; interactive use of next-line and previous-line (holding down C-n or C-p) lag in a buffer with all spaces and newlines jamezmcclain
2016-05-05 16:01 ` Eli Zaretskii
[not found] ` <CAEsaJvOMYP=VtqjdH06Yztagn084yYMe2QW986=nq6nv5pKc4g@mail.gmail.com>
2016-05-05 19:26 ` Eli Zaretskii
2016-05-05 19:59 ` Eli Zaretskii
2016-05-06 0:34 ` James McClain
2016-05-06 7:03 ` Eli Zaretskii
2016-05-06 7:59 ` Nicolas Petton
2016-05-06 8:41 ` Eli Zaretskii
2016-05-06 8:43 ` James McClain [this message]
2016-05-06 9:13 ` Stephen Berman
2016-05-06 9:20 ` Eli Zaretskii
2016-05-06 9:15 ` Eli Zaretskii
2016-05-06 9:19 ` James McClain
2016-05-06 9:24 ` Eli Zaretskii
2016-05-07 8:02 ` 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=CAEsaJvPTBHbrdnmwUvO27A0PAgXN90MZKthKMuAk-_7+nWNgzg@mail.gmail.com \
--to=jamezmcclain@gmail.com \
--cc=23457@debbugs.gnu.org \
--cc=nicolas@petton.fr \
/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).