From: Karl Eichwalder <keichwa@gmx.net>
Subject: fancy splitting
Date: Tue, 18 Mar 2003 21:37:13 +0100 [thread overview]
Message-ID: <shbs0876o6.fsf@tux.gnu.franken.de> (raw)
Documentation on this issue is not that userfriendly; I still cannot
see how it's possible to do the right thing with mails from lists; the
dash in names seems to hurt. This does not work:
(eval-after-load "nnmail"
'(modify-syntax-entry ?- "w" nnmail-split-fancy-syntax-table))
(setq nnmail-split-fancy
'(|
;; List-Post: <mailto:emacs-devel@gnu.org>
;; should end in "nnml:list.emacs-devel"
("List-Post" "mailto:\\b\\(\\w+\\)@.*" "list.\\1")
;; X-BeenThere: emacs-devel@gnu.org
;; should end in "nnml:list.emacs-devel"
("X-BeenThere" "\\b\\(\\w+\\)@.*" "list.\\1")
"mail.rest"))
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.gnu.franken.de/ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
next reply other threads:[~2003-03-18 20:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 20:37 Karl Eichwalder [this message]
2003-03-30 3:21 ` Lars Magne Ingebrigtsen
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=shbs0876o6.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
/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).