From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Gnus is cool
Date: 29 Nov 1999 10:53:28 +1100 [thread overview]
Message-ID: <t4i7lj241hj.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Karl Kleinpaste's message of "Fri, 26 Nov 1999 09:04:25 -0500"
>>>>> "Karl" == Karl Kleinpaste <karl@justresearch.com> writes:
Karl> Hrvoje Niksic <hniksic@iskon.hr> writes:
Karl> No reason to leave it all in some all-encompassing, generic
Karl> archive.
Karl> You could always stuff your contributions right back into
Karl> the same group where they came from, with
Karl> gnus-message-archive-group.
Even better, if you use a MTA that supports receiving mail to
user-extension@hostname.org.au, eg postfix (by default it uses +, not -).
I have
(setq nnmail-split-fancy
[...]
("Delivered-To" "bam-\\(\\w+\\)@snoopy\\.apana\\.org\\.au" "mail.\1")
[...]
)
Now all incoming mail to bam-pgnus@snoopy.apana.org.au, would
automatically end up in the mail.pgnus folder. This means I can
easily manage a number of unrelated tasks.
In order to send mail, I would use:
(setq gnus-posting-styles
'(
[...]
("\\bpgnus\\b"
(signature "Brian May <bam-pgnus@snoopy.apana.org.au>")
(address "bam-pgnus@snoopy.apana.org.au")
("Gcc" "nnml+private:mail.pgnus")
("X-Home-Page" "http://snoopy.apana.org.au/~bam/")
)
[...]
)
What I wish I could do is something like:
(setq gnus-posting-styles
'(
[...]
("mail.\\(\\w+\\)"
(signature "Brian May <bam-\\1@snoopy.apana.org.au>")
(address "bam-\\1@snoopy.apana.org.au")
("Gcc" "nnml+private:mail.\\1")
("X-Home-Page" "http://snoopy.apana.org.au/~bam/")
)
[...]
)
...but this doesn't work. \\1 isn't expanded.
--
Brian May <bmay@csse.monash.edu.au>
prev parent reply other threads:[~1999-11-28 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-26 11:03 Hrvoje Niksic
1999-11-26 14:04 ` Karl Kleinpaste
1999-11-26 14:11 ` Hrvoje Niksic
1999-11-28 23:53 ` Brian May [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=t4i7lj241hj.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).