From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Another posting-styles question
Date: Tue, 26 Aug 2003 00:45:56 +0200 [thread overview]
Message-ID: <m3y8xhmk4b.fsf@defun.localdomain> (raw)
In-Reply-To: <87u1873rcm.fsf@pooh.honeypot.net>
Kirk Strauser <kirk@strauser.com> writes:
> I want to define a set of posting-style "macros" along the lines of:
>
> (setq
> posting-style-generic '(signature-file "~/.signature")
> posting-style-technical '(signature-file "~/.signature-technical"))
>
> and then use them in my Group Parameters like:
>
> ((posting-style
> (posting-style-technical)
> (Organization "The Strauser Group")))
>
> but I can't seem to make the syntax work. The sticking point is when I want
> to make a "macro" with multiple entries. Could someone boot me in the right
> direction?
If you use `gnus-parameters' you can do something like:
(add-to-list 'gnus-parameters
`("some.group" (posting-style
,posting-style-technical
(organization "The Strauser Group"))))
For multiple entries you need to splice the list in with ,@ -- see
<info://elisp/Backquote>.
prev parent reply other threads:[~2003-08-25 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 17:20 Kirk Strauser
2003-08-25 22:45 ` Jesper Harder [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=m3y8xhmk4b.fsf@defun.localdomain \
--to=harder@myrealbox.com \
/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).