From: Tony Lam <Tony.Lam+ding@eng.sun.com>
Cc: ding@gnus.org
Subject: Re: Proposal: eval-ing arbitrary forms via posting-styles.
Date: 26 Jul 1999 16:18:00 -0700 [thread overview]
Message-ID: <4jy6737gfvb.fsf@homeworld.Eng.Sun.Com> (raw)
In-Reply-To: Lloyd Zusman's message of "14 Jul 1999 17:38:43 -0400"
* "Lloyd" == Lloyd Zusman <ljz@asfast.com> writes:
Lloyd> I'm wondering what you folks think of the following idea for an
Lloyd> enhancement to the gnus-posting-styles functionality:
Lloyd> I'd like to be able to eval arbitrary, style-specific forms when
Lloyd> gnus-posting-styles are being processed, without causing any headers
Lloyd> to be set. For example, the syntax might look something like this:
I wonder why it is not already done this way. Group parameters already
allow evaluation of arbitrary forms in summary and article buffer,
posting style should allow the same thing in message buffer. I know it
can be done in message-setup-hook but it is kind of ugly.
Tony
next prev parent reply other threads:[~1999-07-26 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 21:38 Lloyd Zusman
1999-07-26 23:18 ` Tony Lam [this message]
1999-08-27 18:47 ` 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=4jy6737gfvb.fsf@homeworld.Eng.Sun.Com \
--to=tony.lam+ding@eng.sun.com \
--cc=ding@gnus.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).