From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: James Cloos <cloos@jhcloos.com>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 35130@debbugs.gnu.org
Subject: bug#35130: 27.0.50; gnus cannot save
Date: Tue, 30 Apr 2019 14:34:59 -0700 [thread overview]
Message-ID: <877ebbxjlo.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m336lzxk57.fsf@carbon.jhcloos.org> (James Cloos's message of "Tue, 30 Apr 2019 17:23:16 -0400")
On 04/30/19 17:23 PM, James Cloos wrote:
> I found another bug from this change.
>
> (gnus-group-list-level) (A l or A L in the *Group* buffer) has become
> horribly slow and cpu intensive.
>
> It used to be simple and nearly instantaneous.
>
> All of the group-list functions MUST be fast. None of them should
> require any significant work.
I'm not able to reproduce this, the list-level command is pretty much
instantaneous for me. Are you doing this with topic mode on or off? If
it's off, could you edebug `gnus-group-prepare-flat' and see if anything
is obviously taking a bunch of time?
I can't guess what would be slowing the process down that much.
next prev parent reply other threads:[~2019-04-30 21:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-03 21:07 bug#35130: 27.0.50; gnus cannot save James Cloos
2019-04-03 21:53 ` Basil L. Contovounesios
2019-04-03 22:43 ` Eric Abrahamsen
2019-04-04 21:19 ` James Cloos
2019-04-09 18:56 ` Eric Abrahamsen
2019-04-10 11:00 ` James Cloos
2019-04-14 4:42 ` James Cloos
2019-04-21 17:53 ` Eric Abrahamsen
2019-04-22 13:11 ` James Cloos
2019-04-30 18:32 ` James Cloos
2019-04-30 21:19 ` Eric Abrahamsen
2019-04-30 22:54 ` James Cloos
2019-04-30 23:25 ` Eric Abrahamsen
2019-05-01 14:58 ` James Cloos
2019-05-03 19:58 ` Eric Abrahamsen
2019-06-22 12:46 ` Lars Ingebrigtsen
2019-09-27 15:00 ` Lars Ingebrigtsen
2019-04-30 21:23 ` James Cloos
2019-04-30 21:34 ` Eric Abrahamsen [this message]
2019-04-30 22:55 ` James Cloos
2019-04-30 23:18 ` Eric Abrahamsen
2019-04-30 23:52 ` Basil L. Contovounesios
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=877ebbxjlo.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=35130@debbugs.gnu.org \
--cc=cloos@jhcloos.com \
--cc=contovob@tcd.ie \
/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).