From: Eli Zaretskii <eliz@gnu.org>
To: Michael Grant <mgrant@grant.org>
Cc: 72551@debbugs.gnu.org
Subject: bug#72551: 28.2; slowness in global minor mode
Date: Sat, 10 Aug 2024 08:53:51 +0300 [thread overview]
Message-ID: <86wmkokjo0.fsf@gnu.org> (raw)
In-Reply-To: <em0e945ed4-42be-4b27-9bc9-b7a6a211c8e6@4d59a026.com> (bug-gnu-emacs@gnu.org)
> Date: Fri, 09 Aug 2024 18:57:54 +0000
> From: "Michael Grant" via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> To reproduce:
>
> emacs -Q --eval '
> (progn (require (quote cl))
> (load "~/.emacs.d/elpa/yascroll-20220212.1742/yascroll-autoloads.el")
> (cl-loop repeat 100 collect (generate-new-buffer "Test"))
> (global-yascroll-bar-mode 1)
> (setq yascroll:delay-to-hide nil)
> (cl-loop for i below 200 do (insert (format "line %d\n" i)))
> (goto-char (point-min))
> (insert "\n\n --> Now type C-x C-b and see how long it takes!
> <--\n\n"))'
>
> note, you need to have the yascroll package installed. Your package
> directory may vary. This does not seem specific to yascroll, it's just
> easily
> reproduced with yascroll.
>
> The expected result is that it shows the buffer list nearly instantly.
> The actual result is it takes several seconds!
>
> It seems like something is looping over each buffer and calling
> something on each buffer to see if yascroll needs to be enabled.
>
> If a bugfix is not forthcoming, a workaround would be appreciated!
Yascroll is not part of Emacs, and there are several issues about
slowdown on its GitHub site. My suggestion is to take this up with
yascroll's developers.
The first step towards finding the culprit and potential workarounds
is to profile the slow operation with the Emacs Lisp profiler.
next prev parent reply other threads:[~2024-08-10 5:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 18:57 bug#72551: 28.2; slowness in global minor mode Michael Grant via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-10 5:53 ` Eli Zaretskii [this message]
2024-08-17 9:37 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wmkokjo0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72551@debbugs.gnu.org \
--cc=mgrant@grant.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.