From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: gnus-posting-styles vs compose-mail
Date: Thu, 31 Jul 2014 10:10:56 +0800 [thread overview]
Message-ID: <8738diz39r.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87mwbssfqu.fsf@blah.blah>
Kevin Ryde <user42_kevin@yahoo.com.au> writes:
> Does gnus-posting-styles rules have anything to notice when a message
> has been started by `compose-mail', and perhaps the parameters on that
> compose-mail?
>
> I see dynamic bindings of the compose-mail args are visible as variables
> `to', `subject', etc, but I wonder if that should be relied on.
>
> I thought to suppress Gcc on some semi-automated mails. I got the
> effect I wanted from code in gnus-message-archive-group like below, and
> then wondered if it too already had anything to notice compose-mail or
> match headers. (At the gnus-message-archive-group stage the buffer has
> headers ready to consult, I believe.)
>
> (setq gnus-message-archive-group
> '((if (equal (message-fetch-field "To") "query@example.com")
> nil
> "sent")))
I think no, posting styles won't look at the headers of messages you
compose. My understanding is the styles are only in effect for a) group
names, when you're composing a message to a specific group, and b)
messages you're replying to, in which case the styles match on the
headers of the original (received) message. I don't think you can do it
based on outgoing message headers. How would gnus know which of the
gnus-posting-style entries were meant to match on outgoing messages, and
which meant to match on replied messages?
I've thought off and on about a wrapper for mail composition, which
would first query you for a few headers, and then set up the message
accordingly. That would provide a place to run hooks like what you want,
but until someone writes that wrapper...
Yours,
Eric
next prev parent reply other threads:[~2014-07-31 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 8:58 Kevin Ryde
2014-07-31 2:10 ` Eric Abrahamsen [this message]
2014-08-02 3:44 ` Kevin Ryde
2014-08-04 2:12 ` Eric Abrahamsen
2014-09-12 23:55 ` jenia.ivlev
2014-09-13 8:29 ` Andreas Schwab
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=8738diz39r.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).