unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Andreas Schwab <schwab@linux-m68k.org>,
	53352@debbugs.gnu.org
Subject: bug#53352: 29.0.50; IMAP INBOX not refreshing using `gnus-group-get-new-news'
Date: Mon, 24 Jan 2022 10:48:27 -0800	[thread overview]
Message-ID: <87zgnl55s4.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8735ldc8jv.fsf@md5i.com> (Michael Welsh Duggan's message of "Mon, 24 Jan 2022 13:06:44 -0500")


On 01/24/22 13:06 PM, Michael Welsh Duggan wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> On 01/24/22 17:34 PM, Andreas Schwab wrote:
>>> On Jan 24 2022, Michael Welsh Duggan wrote:
>>>
>>>> This appears to be happening in `gnus-get-unread-articles' in the
>>>> initial `let*'.  "INBOX" is the car of `gnus-newsrc-alist', and `newsrc'
>>>> is explicitly set to the cdr of that list.
>>>
>>> The first element of gnus-newsrc-alist is supposed to be the
>>> dummy.group, but that doesn't appear to be the case any more.  Can this
>>> be related to commit a09306d53b?
>>
>> Yup, looks like that's the problem. After the first time you save Gnus,
>> `gnus-newsrc-alist' has been redefined to exclude "dummy.group". It
>> should be easy to fix -- I'll move the sorting and exclusion into the
>> `let', which will preserve the variable's original value.
>
> To be clear, would this mean I need to add "dummy.group" to my
> `gnus-newsrc-alist' after you make this change, or will the change
> obviate the need for the dummy entry?  If the former, would you please
> verify the form I need to prepend to the alist?  Is it just the
> "dummy.group" string?

You won't have to do anything. With the code as it is, the dummy group
is present at Gnus startup, but gets deleted on first save. I'll put in
a fix that makes sure it doesn't get deleted. That should take care of
things.

There's no longer any need for a dummy group, and in the long run it
would be good to get rid of it. But I think in short term we still think
there's a significant amount of out-of-tree code that might be expecting
a dummy group.

Eric





  reply	other threads:[~2022-01-24 18:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 23:07 bug#53352: 29.0.50; IMAP INBOX not refreshing using `gnus-group-get-new-news' Michael Welsh Duggan
2022-01-21 10:29 ` Lars Ingebrigtsen
2022-01-22 16:25   ` Michael Welsh Duggan
2022-01-23 12:58     ` Lars Ingebrigtsen
2022-01-23 16:55       ` Michael Welsh Duggan
2022-01-24  9:18         ` Lars Ingebrigtsen
2022-01-24 16:15           ` Michael Welsh Duggan
2022-01-24 16:33             ` Lars Ingebrigtsen
2022-01-24 16:34             ` Andreas Schwab
2022-01-24 17:59               ` Eric Abrahamsen
2022-01-24 18:06                 ` Michael Welsh Duggan
2022-01-24 18:48                   ` Eric Abrahamsen [this message]
2022-01-24 18:31                 ` Lars Ingebrigtsen
2022-01-24 19:20                   ` Eric Abrahamsen
2022-01-24 21:15                     ` Michael Welsh Duggan
2022-01-24 22:18                       ` Eric Abrahamsen
2022-01-31 14:32                         ` Michael Welsh Duggan
2022-01-31 19:27                           ` Eric Abrahamsen
2022-02-07 10:49                     ` Andreas Schwab
2022-02-07 16:50                       ` Eric Abrahamsen
2022-02-07 17:42                         ` Andreas Schwab
2022-02-07 21:17                           ` Eric Abrahamsen
2022-02-07 21:34                             ` Andreas Schwab
2022-02-07 23:51                               ` Eric Abrahamsen
2022-02-09  4:38                               ` Eric Abrahamsen
2022-02-09  8:45                                 ` Andreas Schwab
2022-02-10 19:38                                   ` 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

  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=87zgnl55s4.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=53352@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=mwd@md5i.com \
    --cc=schwab@linux-m68k.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 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).