Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Rychter <jan@rychter.com>
Subject: Re: [PATCH] add option to posting styles
Date: Mon, 23 Jun 2003 19:42:56 -0700	[thread overview]
Message-ID: <m24r2ggpqn.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <848yrsh87j.fsf@lucy.is.informatik.uni-duisburg.de> (Kai =?iso-8859-1?q?Gro=DFjohann's?= message of "Mon, 23 Jun 2003 22:04:00 +0200")

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

>>>>> "Kai" == Kai Großjohann <kai.grossjohann@gmx.net>:
 Kai> Jan Rychter <jan@rychter.com> writes:
 >> What I need is a hook that is run just before the user starts
 >> editing the message, but after the text to be cited (being replied
 >> to) has been properly inserted.
 >>
 >> mail-citation-hook is close, but seems to be designed for something
 >> else.

 Kai> Ayee.  Maybe message-cite-function is what you need.  But it's not
 Kai> the right thing to use.  Argh.

 Kai> So maybe what the world needs is another hook,
 Kai> message-after-yank-hook?

That's how I see it -- unless there is something I'm missing.

I'll try to summarize the discussion:

  -- I would like to be able to specify in gnus-posting-styles that I
     want certain messages to be PGP signed, which can't be done at
     present,
  -- I have added a "call" option to gnus-posting-styles, that permits
     one to supply a function that will be added to the appropriate
     hook,
  -- then I found out that there is no "appropriate hook": because of
     the way MML is designed, it wants to insert a line into the message
     being written _no earlier than_ after the cited text has been
     yanked. If we insert the MML tag earlier, it will get cited,
  -- an additional constraint is that the MML tag should be there when
     I'm composing the message: I'd like to be sure the message is going
     to be signed. So message-send and similar hooks won't do.

There are some options:

  -- fix supercite (and everything else people might be using for citing
     text) to recognize MML tags and work around them,
  -- hack MML to do something special about some special headers,
  -- make a "mml-something-hook" that will be designed specifically for
     the purpose of letting MML know about things,
  -- add another hook to message, as Kai described.

I do not think I'm knowledgeable enough to decide which is better.

--J.

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

      reply	other threads:[~2003-06-24  2:42 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
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 [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=m24r2ggpqn.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).