From: Thien-Thi Nguyen <ttn@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: splitting weird on emacs trunk gnus
Date: Mon, 07 Jul 2014 17:45:49 +0200 [thread overview]
Message-ID: <87oax1jhoy.fsf@zigzag.favinet> (raw)
In-Reply-To: <87simdjij3.fsf@zigzag.favinet> (Thien-Thi Nguyen's message of "Mon, 07 Jul 2014 17:27:44 +0200")
[-- Attachment #1.1: Type: text/plain, Size: 729 bytes --]
() Thien-Thi Nguyen <ttn@gnu.org>
() Mon, 07 Jul 2014 17:27:44 +0200
Anyone else see similar weirdness?
Yes, you fool! Obviously you haven't read:
(info "(gnus) Client-Side IMAP Splitting")
and done:
(setq gnus-secondary-select-methods
'(...
(nnimap ...
(nnimap-split-methods 'default)
)
))
in ~/.gnus ! Stop wasting everyone's time!
(BTW, i really dislike both ‘RET’ and ‘C-j’ indenting, WTF!)
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-07-07 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 15:27 Thien-Thi Nguyen
2014-07-07 15:45 ` Thien-Thi Nguyen [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=87oax1jhoy.fsf@zigzag.favinet \
--to=ttn@gnu.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).