From: Michael Welsh Duggan <mwd@md5i.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Michael Welsh Duggan <mwd@md5i.com>, 53352@debbugs.gnu.org
Subject: bug#53352: 29.0.50; IMAP INBOX not refreshing using `gnus-group-get-new-news'
Date: Sat, 22 Jan 2022 11:25:02 -0500 [thread overview]
Message-ID: <874k5vg2ld.fsf@md5i.com> (raw)
In-Reply-To: <87o845tm9b.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 21 Jan 2022 11:29:36 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Michael Welsh Duggan <mwd@md5i.com> writes:
>
>> I have a gnus installation where the select method is as such:
>>
>> ;;; Select Method
>> (setq gnus-select-method
>> '(nnimap "localimap"
>> (nnimap-inbox "INBOX")
>> (nnimap-address "xxxxxxxx.xxx")))
>
> If you're not using Gnus to split the mail, wouldn't it make more sense
> to leave nnimap-inbox as nil?
Likely. This is a leftover from when I was using Gnus to do splitting
instead of sieve. However, removing the `nnimap-inbox' clause and
restarting Gnus does not cause the unwanted behavior to change.
>> Mail splitting is currently being handled by sieve, not by Gnus.
>> However, when sieve leaves a message in INBOX rather than sorting it to
>> another folder, it does not appear in INBOX using `g'
>> (gnus-group-get-new-news). Any mail that stays there does show up if I
>> use `M-g' (gnus-topic-get-new-news-this-topic) on the group. This only
>> happens for the INBOX folder. I don't believe INBOX should behave
>> differently from other folders in this regard.
>
> I don't see any special handling of the folder called INBOX in nnimap.
> Do you have the INBOX group on a too-high level? You said you're using
> a group activation level of 1, but not what the level of the INBOX group
> was.
INBOX is at level 1.
--
Michael Welsh Duggan
(md5i@md5i.com)
next prev parent reply other threads:[~2022-01-22 16:25 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 [this message]
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
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=874k5vg2ld.fsf@md5i.com \
--to=mwd@md5i.com \
--cc=53352@debbugs.gnu.org \
--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 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).