From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 36341@debbugs.gnu.org, Deus Max <deusmax@gmx.com>
Subject: bug#36341: 27.0.50; Reading from the Gnus dribble file leaves data inconsistent
Date: Mon, 08 Jul 2019 21:53:56 -0700 [thread overview]
Message-ID: <87muhnzu3f.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m3tvbw1l7f.fsf@gnus.org> (Lars Ingebrigtsen's message of "Mon, 08 Jul 2019 19:37:40 +0200")
On 07/08/19 19:37 PM, Lars Ingebrigtsen wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Okay, I get that. But I wonder how important it is that add/delete
>> operations be so efficient? Does subscription/unsubscription happen so
>> often that it needs to be fast?
>
> It's annoying if, say, killing ten groups takes a long time (and the
> user may have tens of thousands of subscribed groups)...
Okay, I am happy to look at that part of the code and see if we can do
the deletions/insertions in bulk, after the group levels have been
changed. Either way, I don't think this has to be a serious speed
breaker for Gnus.
next prev parent reply other threads:[~2019-07-09 4:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 14:30 bug#36341: 27.0.50; Reading from the Gnus dribble file leaves data inconsistent Lars Ingebrigtsen
2019-06-23 15:34 ` Eric Abrahamsen
2019-06-23 15:41 ` Lars Ingebrigtsen
2019-06-23 16:35 ` Eric Abrahamsen
2019-06-23 18:25 ` Deus Max
2019-06-23 18:38 ` Eric Abrahamsen
2019-06-23 18:40 ` Lars Ingebrigtsen
2019-06-28 22:30 ` Eric Abrahamsen
2019-06-29 10:22 ` Lars Ingebrigtsen
2019-07-03 19:46 ` Eric Abrahamsen
2019-07-04 13:43 ` Lars Ingebrigtsen
2019-07-05 19:24 ` Eric Abrahamsen
2019-07-06 12:06 ` Lars Ingebrigtsen
2019-07-07 23:56 ` Eric Abrahamsen
2019-07-08 16:22 ` Lars Ingebrigtsen
2019-07-08 17:29 ` Eric Abrahamsen
2019-07-08 17:37 ` Lars Ingebrigtsen
2019-07-09 4:53 ` Eric Abrahamsen [this message]
2019-07-09 17:50 ` Eric Abrahamsen
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=87muhnzu3f.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36341@debbugs.gnu.org \
--cc=deusmax@gmx.com \
--cc=larsi@gnus.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.