From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: wrong unread count after INBOX change
Date: Tue, 05 Jan 2016 17:55:17 +0800 [thread overview]
Message-ID: <871t9wxse2.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2vb78e4l6.fsf@charm-ecran.irisa.fr>
Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> On 2016-01-05 17:18, Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>>
>>> Hello,
>>>
>>> As I modified my dovecot configuration, I had to change where the INBOX
>>> is stored. It should have been transparent to gnus (I access my mail
>>> locally through dovecot) but for some reason it confused it and gnus now
>>> believe I have 3900 unread message in this INBOX, although there is
>>> none. I tried doing 'g' and 'M-g' on it but it does not change anything.
>>> If I hit 'ret' I get an error "Can't select group", and if I it 'C-u
>>> ret' I see the expected 27 read messages.
>>>
>>> How can I convince gnus to reset its unread count for this mailbox?
>>
>> The sure-fire rip-cord solution for this sort of situation is to edit
>> the group parameters for that group, completely delete the (active .
>> XXXX) sexp, finish the edits, then M-g on the group again.
>>
>> Works most every time, for me!
>>
>> Of course, I can't currently confirm this, because editing a group in
>> the Group buffer currently gives me:
>>
>> gnus-group-edit-group: Symbol’s function definition is void:
>> gnus-format-message
>
> I'm seeing the same thing, but I can still edit using 'G c' (edit
> through customize interface). Unfortunately it does not change anything:
> as soon as I 'M-g' on it I get back the same active sexp.
>
> I also tried removing the "modseq" sexp, to no avail.
Oops, that was the only weapon in my arsenal. I suppose you might
consider just removing the server and re-adding it. I don't know what
else can be done.
next prev parent reply other threads:[~2016-01-05 9:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 9:04 Alan Schmitt
2016-01-05 9:18 ` Eric Abrahamsen
2016-01-05 9:32 ` Eric Abrahamsen
2016-01-06 3:41 ` Dave Goldberg
2016-01-06 9:17 ` Eric Abrahamsen
2016-01-06 10:07 ` Eric Abrahamsen
2016-01-06 11:20 ` Eric Abrahamsen
2016-01-05 9:52 ` Alan Schmitt
2016-01-05 9:55 ` Eric Abrahamsen [this message]
2016-01-05 10:32 ` Alan Schmitt
2016-01-05 11:02 ` CHENG Gao
2016-01-05 13:41 ` Alan Schmitt
2016-01-05 11:08 ` Eric Abrahamsen
2016-01-05 13:44 ` Alan Schmitt
2016-01-05 15:13 ` 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=871t9wxse2.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@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.
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 NNTP newsgroup(s).