From: Kevin Ryde <user42_kevin@yahoo.com.au>
To: ding@gnus.org
Subject: Re: gnus-posting-styles vs compose-mail
Date: Sat, 02 Aug 2014 13:44:59 +1000 [thread overview]
Message-ID: <87iombo8qs.fsf@blah.blah> (raw)
In-Reply-To: <8738diz39r.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Thu, 31 Jul 2014 10:10:56 +0800")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> I think no, posting styles won't look at the headers of messages you
> compose.
Hmm, yes, a bit early.
> 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?
Oh, it would have to be some different pattern form or something.
I suppose there's only a few common compose-mail starts.
M-x report-emacs-bug or M-x debian-bug would be main ones.
next prev parent reply other threads:[~2014-08-02 3:44 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
2014-08-02 3:44 ` Kevin Ryde [this message]
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=87iombo8qs.fsf@blah.blah \
--to=user42_kevin@yahoo.com.au \
--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).