From: Gijs Hillenius <gijs@hillenius.net>
To: help-gnu-emacs@gnu.org
Subject: reopened bug#20610 emacs25.1 is not reading or resetting nnimap-split-fancy
Date: Fri, 14 Oct 2016 15:37:06 +0200 [thread overview]
Message-ID: <87lgxroxvh.fsf@hillenius.net> (raw)
I reopened Emacs bug bug#20610, for I'm experiencing something
similar. Using the new Emacs25 package in Debian, which provides GNU
Emacs 25.1.1, the gnus.el file is read, but for some reason
nnimap-split-fancy is reset.
Upon firing up Gnus, the value if nnmimap-split-fancy is nil, and so
(bbdb/gnus-split-method) does not work. I use that alot, which is how I
noticed the 'bug'.
So I reload my nnimap-split-fancy set-up, and of course, fancy split
then works. The value of nnimap-split-fancy confirms.
Other settings in gnus.el are not reset, such as for instance
(setq bbdb-default-country "Netherlands")
next reply other threads:[~2016-10-14 13:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 13:37 Gijs Hillenius [this message]
2016-10-14 13:48 ` reopened bug#20610 emacs25.1 is not reading or resetting nnimap-split-fancy Gijs Hillenius
2016-10-17 1:34 ` Glenn Morris
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=87lgxroxvh.fsf@hillenius.net \
--to=gijs@hillenius.net \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).