Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
Subject: Re: [PATCH] add option to posting styles
Date: Thu, 19 Jun 2003 13:59:50 -0700	[thread overview]
Message-ID: <m2el1pdbqx.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <m2smq5er5d.fsf@tnuctip.rychter.com> (Jan Rychter's message of "Thu, 19 Jun 2003 13:41:50 -0700")

[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]

>>>>> "Jan" == Jan Rychter <jan@rychter.com> writes:
 Jan> The following patch adds another option to posting styles, which
 Jan> allows one to add custom functions to mesage-setup-hook. The
 Jan> existing 'eval' functionality was not enough, because some
 Jan> functions expect the other headers (and mail-header-separator) to
 Jan> already be there when they get called,
 Jan> mml-secure-message-sign-pgpmime is an example.

 Jan> Thanks to this I can now define

 Jan> (setq gnus-posting-styles '((".*icm\\.misc" (call
 Jan> mml-secure-message-sign-pgpmime))))

 Jan> ... and have all messages in the groups maching the regexp
 Jan> automatically signed.

[time passes]

Well, that won't really work. It works for new messages, but doesn't
work for replies. The reason is that posting styles get applied very
early in the process, so after mml-secure-message-sign-pgpmime inserts
<\#secure method=pgpmime mode=sign>, supercite happily inserts the cited
text and cites the mml marker as well.

What I'm trying to do is somewhat similar to what
gnus-summary-handle-replysign does. But I noticed that
gnus-summary-reply cheats and runs gnus-summary-handle-replysign at the
very end, after everything else is done. There is no way I can do this
with posting styles, right?

Hmm. Or can we call gnus-configure-posting-styles after the message has
been set up? What would be a good solution here?

--J.

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2003-06-19 20:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 20:41 Jan Rychter
2003-06-19 20:59 ` Jan Rychter [this message]
2003-06-20  7:19   ` Kai Großjohann
2003-06-20  8:05     ` Jan Rychter
2003-06-20 14:45       ` Kai Großjohann
2003-06-23 23:44       ` Lars Magne Ingebrigtsen
2003-06-27 13:17         ` Jan Rychter
2003-10-17 23:38           ` Lars Magne Ingebrigtsen
2003-06-23  8:29     ` Jan Rychter
2003-06-23 20:04       ` Kai Großjohann
2003-06-24  2:42         ` Jan Rychter

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=m2el1pdbqx.fsf@tnuctip.rychter.com \
    --to=jan@rychter.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).