GNU bug report logs - #36341
27.0.50; Reading from the Gnus dribble file leaves data inconsistent

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#36341: closed (Re: bug#36341: 27.0.50; Reading from the Gnus
 dribble file leaves data inconsistent)
Date: Tue, 09 Jul 2019 17:51:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#36341: 27.0.50; Reading from the Gnus dribble file leaves data inconsistent

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 36341 <at> debbugs.gnu.org.

-- 
36341: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=36341
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 36341-done <at> debbugs.gnu.org, 36341 <at> debbugs.gnu.org,
 Deus Max <deusmax <at> gmx.com>
Subject: Re: bug#36341: 27.0.50;
 Reading from the Gnus dribble file leaves data inconsistent
Date: Tue, 09 Jul 2019 10:50:43 -0700

Eric Abrahamsen <eric <at> ericabrahamsen.net> writes:

> On 07/08/19 19:37 PM, Lars Ingebrigtsen wrote:
>> Eric Abrahamsen <eric <at> 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.

And I'm going to close this particular report for now, and go back to
working on completion of the larger patch set.

[Message part 3 (message/rfc822, inline)]

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0.50; Reading from the Gnus dribble file leaves data inconsistent
Date: Sun, 23 Jun 2019 16:30:30 +0200

If I have the following in my Gnus dribble file

(gnus-group-set-info '("nntp+news.gmane.org:gwene.org.jwz.blog.comments" 3 ((1 . 25172)) ((unexist) (seen (1 . 1032) (1044 . 5020) (5022 . 11580) (11629 . 15722) (15725 . 19758) (19774 . 25172))) "nntp:news.gmane.org"))

and start Gnus, then the group buffer will then always show the same
unread count as existed in the previous Gnus session.  Entering the
group and marking everything as read has no effect -- the group still
shows the old number of unread articles.


In GNU Emacs 27.0.50 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.22.11)
 of 2019-06-23 built on stories
Repository revision: abf7d0d802728e0ae8e064683eb5fb411bad911e
Repository branch: master
Windowing system distributor 'The X.Org Foundation', version 11.0.11902000
System Description: Debian GNU/Linux 9 (stretch)


-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.