unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Welsh Duggan <mwd@md5i.com>
Cc: 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:18:51 +0100	[thread overview]
Message-ID: <87ee4x5w5g.fsf@gnus.org> (raw)
In-Reply-To: <87iluae6ij.fsf@md5i.com> (Michael Welsh Duggan's message of "Sun, 23 Jan 2022 11:55:32 -0500")

Michael Welsh Duggan <mwd@md5i.com> writes:

> I'm not going to send the whole list unless you believe it's necessary.
> The log (after `g') consists of 122 lines as follows:
>
> 11:42:43 [md5i.com] 91340 EXAMINE "mail.misc" (QRESYNC (1044651295 71865))
> 11:42:43 [md5i.com] 91341 EXAMINE "mail.junk" (QRESYNC (1162282036 126251))
>
> (I removed the ^M at the end of log lines for this email.)  This list
> does not contain "INBOX".  If you actually need the full list, I can
> send it, but the line above is representative of them all.

When I try the same, I do get INBOX in the list of EXAMINES:

10:14:57 [quimby.gnus.org] 12526 EXAMINE "Sent" (QRESYNC (1457952636 8))
10:14:57 [quimby.gnus.org] 12527 EXAMINE "INBOX" (QRESYNC (1164213559 1225378))

So it sounds like somehow your Gnus is deciding not to activate the
INBOX group (because of some setting or other, I'd guess).  I'm not sure
how you could debug that -- perhaps debug-on-entry on
nnimap-retrieve-group-data-early and see where the list of `infos' is
coming from, and see whether it includes INBOX and whether it's being
filtered out?

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





  reply	other threads:[~2022-01-24  9:18 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 [this message]
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
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=87ee4x5w5g.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=53352@debbugs.gnu.org \
    --cc=mwd@md5i.com \
    /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).