From: Greg Stark <gsstark@mit.edu>
Subject: nnimap-expunge-on-close, this damn variable just won't die
Date: 03 Jan 2001 00:58:57 -0500 [thread overview]
Message-ID: <87elyl5g7y.fsf@localhost.freelotto.com> (raw)
I keep setting nnimap-expunge-on-close to 'never over and over again. And it
keeps being reset to 'always. I set it in my .emacs after loading nnimap, I
set it again after loading gnus because it seems to be set to 'always, and
just now after reading for a while it spontaneously got set to 'always yet
again.
This is most frustrating as trying to expunge my inbox takes an extremely long
time and since there's no expiry it's completely futile. (Yes, these facts may
be related...)
Why on earth does it keep getting reset? I can't find anything that would be
responsible anywhere in the source. The only thing I suspect is the nnoo black
magic.
--
greg
reply other threads:[~2001-01-03 5:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87elyl5g7y.fsf@localhost.freelotto.com \
--to=gsstark@mit.edu \
/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).