Gnus development mailing list
 help / color / mirror / Atom feed
From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Re: Yet another attempt at more signing
Date: Thu, 28 Mar 2002 12:56:42 -0800	[thread overview]
Message-ID: <861ye4s96b.fsf@duchess.twilley.org> (raw)
In-Reply-To: <m34rj0pjaa.fsf@multivac.cwru.edu>

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

>>>>> "Paul" == Paul Jarc <prj@po.cwru.edu> writes:

[...]

Paul> What about this: (setq mail-header-separator "") (add-hook
Paul> 'message-send-news-hook 'jmt:message-send-news-hook) (defun
Paul> jmt:message-send-news-hook () (if (not (string=
Paul> "one.particular.newsgroup" gnus-newsgroup-name))
Paul> (mml-secure-message-sign-pgpmime)))

The message-send-news-hook is too late to do what I need.  That is
after the time where Gnus checks to see if the tag is there.  All that
function will do at that time is add that line, which isn't helpful.

Paul> (I always give hook functions names so that I can redefine the
Paul> function during testing, rather than having to remove the old
Paul> version from the hook, which is easy to forget.)

A good practice, I agree.  When I'm first tweaking something, I don't
usually do that, though.

Paul> paul

Jack.
(ah, elisp)
-- 
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash

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

      reply	other threads:[~2002-03-28 20:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 13:47 Jack Twilley
2002-03-27 17:49 ` Simon Josefsson
2002-03-28  0:09   ` Jack Twilley
2002-03-28  0:12   ` Paul Jarc
2002-03-28 10:26     ` Simon Josefsson
2002-03-28 18:09       ` Simon Josefsson
2002-03-28 19:25         ` Jack Twilley
2002-03-28 19:40           ` Jack Twilley
2002-03-28 19:46           ` Paul Jarc
2002-03-28 20:56             ` Jack Twilley [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=861ye4s96b.fsf@duchess.twilley.org \
    --to=jmt+usenet@twilley.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).