Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ilan Pillemer <not.relevant@all.org>
To: info-gnus-english@gnu.org
Subject: Re: imap, keeps trying even after removing from gnus.el
Date: Sun, 04 Sep 2016 21:13:58 +0100	[thread overview]
Message-ID: <m2k2erv2wp.fsf@Ilans-MBP-2.home> (raw)
In-Reply-To: <8760qckusi.fsf@hillenius.net>

Gijs Hillenius <gijs@hillenius.net> writes:

> On  3 Sep 2016, Ilan Pillemer wrote:
>
>
>> I have removed the secondary select method for IMAP from my .gnus.el
>>
>> However, gnus doesn't care and keeps trying to connect when I start
>> gnus.
>>
>> How can I make it care?
>
>
> Is it also removed from the *Server* buffer?
>
>
> to check: type ^ in the *Group* buffer

Thanks! It was still there.

It's gone now.

--
Ilan

      reply	other threads:[~2016-09-04 20:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2mvjolom3.fsf@Ilans-MBP-2.home>
2016-09-04  7:07 ` Gijs Hillenius
2016-09-04 20:13   ` Ilan Pillemer [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=m2k2erv2wp.fsf@Ilans-MBP-2.home \
    --to=not.relevant@all.org \
    --cc=info-gnus-english@gnu.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).