Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ryan Kavanagh via "Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader \(in English\)" <info-gnus-english@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Subscribing to nnimap folders that are subscribed on IMAP servers
Date: Mon, 01 Aug 2022 17:56:45 -0400	[thread overview]
Message-ID: <87a68nsk4i.fsf@rak.ac> (raw)
In-Reply-To: <87czdl5lse.fsf@ericabrahamsen.net>

On Sun, Jul 31 2022, Eric Abrahamsen wrote:
> Best to read the "New Groups" section of the Gnus manual: that will give
> you the background on `gnus-check-new-newsgroups' (you could also read
> its docstring), as well as methods of subscribing to new groups.
>
> Let us know if that doesn't clear it up!

gnus-check-new-newsgroups, if set, causes Gnus to call
gnus-find-new-newsgroups at startup, which then subscribes gnus to IMAP
folders according to the value of gnus-subscribe-newsgroup-method.

I tried running gnus-find-new-newsgroups with the method set to the
default (gnus-subscribe-zombies). Unfortunately, subscribing to a folder
in Gnus causes it to become subscribed *on the IMAP server itself* (I
believe thanks to nnimap-request-update-group-status). In particular,
gnus-find-new-newsgroups caused all of my IMAP folders to get marked as
subscribed on the server, which is definitely not what I
wanted. (Fortunately, I was able to restore my subscriptions from backup...)

I suppose I could set the method gnus-subscribe-interactively and
manually decide whether or not I want to subscribe to each folder in
gnus, but this would be very tedious: I have close to 200 folders spread
across my various IMAP accounts. I am not (IMAP-)subscribed to the vast
majority of these, and I do not want gnus to be subscribed to them
either.

Do you have any suggestions on how I can have gnus subscribe to just
those groups in the output of LSUB / LIST (SUBSCRIBED) [0]? I don't see
any functionality for doing so in the code base, so I suspect that this
might be a feature request...

Thanks,
Ryan

[0] https://datatracker.ietf.org/doc/html/rfc9051#section-6.3.9.1

--
|)|/  Ryan Kavanagh  | 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac | BD95 8F7B F8FC 4A11 C97A



      reply	other threads:[~2022-08-01 21:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 15:11 Ryan Kavanagh via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2022-07-31 15:44 ` Eric Abrahamsen
2022-08-01 21:56   ` Ryan Kavanagh via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English) [this message]

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=87a68nsk4i.fsf@rak.ac \
    --to=info-gnus-english@gnu.org \
    --cc=rak@rak.ac \
    /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).