From: ndame <emacsuser@freemail.hu>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: 26.2; Strange slowness in some Info nodes
Date: Fri, 2 Aug 2019 15:37:52 +0000 (GMT) [thread overview]
Message-ID: <Axvg1g.huuIFOYZps.phJUTTX544aUaguVABt@freemail.hu> (raw)
I don't know if it's a known bug or some system dependent issue
that's why I'm sending it to help.
I recently moved to emacs 26 and today I noticed a strange
scrolling slowdown in certain Info nodes.
It also occurs with emacs -q.
If I go to Elisp info and try to scroll in the main index with
page up/down then everything is fine and quick.
If I go to Lists and then to Building Lists and there try to
scroll down with page down, then the scrolling becomes slow, like
it takes one second for emacs to scroll the page after pressing
page down/up.
The problem seems to occur only in info nodes where there are
separate sections describing entities like functions in Building
Lists:
-- Function: cons object1 object2
This function is the most basic function for building new list
structure. It creates a new cons cell, making OBJECT1 the CAR,
and OBJECT2 the CDR. It then returns the new cons cell. The
arguments OBJECT1 and OBJECT2 may be any Lisp objects, but most
often OBJECT2 is a list.
In nodes with free flow text there is no problem with scrolling, so
it's like info does something extra in entity describing nodes.
It's 26.2 on Windows taken from the official GNU site:
GNU Emacs 26.2 (build 1, x86_64-w64-mingw32) of 2019-04-13
The problem also occurred with 26.1 I upgraded to 26.2. but it's
the same there.
Does anyone else experience this? Is this a known issue?
next reply other threads:[~2019-08-02 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 15:37 ndame [this message]
2019-08-02 18:53 ` 26.2; Strange slowness in some Info nodes Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-08-02 19:24 ndame
2019-08-02 19:58 ` Eli Zaretskii
2019-08-02 19:49 Joe_Trivers
2019-08-02 20:23 ndame
2019-08-03 6:48 ` 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=Axvg1g.huuIFOYZps.phJUTTX544aUaguVABt@freemail.hu \
--to=emacsuser@freemail.hu \
--cc=help-gnu-emacs@gnu.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.
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).