From: James Hudon <jameshudon@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 14259@debbugs.gnu.org
Subject: bug#14259: 24.1; global-linum-mode slows down scrolling and user input in DocView
Date: Wed, 24 Apr 2013 16:57:27 -0400 [thread overview]
Message-ID: <CAGtM-BejA9gamKG+ax+2VOkZ6GtgSp3WwpKibYjRf3U1V7Hb7w@mail.gmail.com> (raw)
In-Reply-To: <jwvehdz3h90.fsf-monnier+emacs@gnu.org>
Yes, with nlinum-mode, I don't notice the lag at all.
I should add the problem gets much worse as the document you're using
grows, which would explain why the lag you're getting is worse than a
"noticeable lag". With a 20-page doc, it's just really annoying. With
a 50-page doc [1], Emacs is completely unusable.
[1] a 50-page pdf:
http://www.symantec.com/content/en/us/enterprise/media/security_response/whitepapers/w32_stuxnet_dossier.pdf
hudon
On Wed, Apr 24, 2013 at 2:47 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> 2. Open a PDF that has pages you can scroll
> [...]
>> 5. Ensure the global-linum-mode is enabled and now scroll around/change
>> pages/etc. There should be a noticeable lag that makes it very hard to use
>
> Indeed, I can reproduce it, and it's not just a "noticeable lag" for me,
> it's so dog slow that it makes you feel like Emacs is failing to respond.
>
>> Does it help to use nlinum from GNU ELPA instead?
>
> Yes, it's much faster. With nlinum-mode, there is still a slowdown
> (slightly more noticeable for horizontal scrolls than vertical scrolls),
> but it's much less severe.
> You can see the exact same slow down if you just do:
>
> M-: (set-window-margins (selected-window) 2) RET
>
> So the performance cost doesn't come from nlinum-mode.
> As for linum-mode, I'm not sure where the performance problem lies.
>
>
> Stefan
next prev parent reply other threads:[~2013-04-24 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:24 bug#14259: 24.1; global-linum-mode slows down scrolling and user input in DocView James Hudon
2013-04-24 16:53 ` Glenn Morris
2013-04-24 18:47 ` Stefan Monnier
2013-04-24 20:57 ` James Hudon [this message]
2020-08-21 14:06 ` Stefan Kangas
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=CAGtM-BejA9gamKG+ax+2VOkZ6GtgSp3WwpKibYjRf3U1V7Hb7w@mail.gmail.com \
--to=jameshudon@gmail.com \
--cc=14259@debbugs.gnu.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).