unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jens Lechtenboerger <jens.lechtenboerger@fsfe.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Yuri D'Elia <wavexx@thregr.org>, emacs-devel@gnu.org
Subject: Re: message.el and mml-secure-bcc-is-safe
Date: Sun, 22 Jan 2017 14:44:20 +0100	[thread overview]
Message-ID: <874m0rgqff.fsf@informationelle-selbstbestimmung-im-internet.de> (raw)
In-Reply-To: <87y3y49xt7.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 21 Jan 2017 17:34:28 +0100")

On 2017-01-21, at 17:34, Lars Ingebrigtsen wrote:

> Yuri D'Elia <wavexx@thregr.org> writes:
>
>> I'd like to manipulate the mml tags on the message inside the
>> 'message-send-hook depending on the recipient.
>>
>> By reading though message.el, this seems to be possible as the hook is
>> ran early enough.
>>
>> However, I notice that (mml-secure-bcc-is-safe) is called before the
>> hook. If I plan to modify the tags, it actually makes sense to run it
>> just afterwards instead so that it checks the final headers and tags.
>>
>> Could we move (mml-secure-bcc-is-safe) just after the hook?
>> It makes more sense to me, unless there's some specific reason to do so.
>
> I'm not sure...  there might be subtleties there...  I've added Jens to
> the Cc; he added the code so he might have an opinion.

There was no particular reason for adding the bcc-check before
executing that hook.  Feel free to exchange their order.

Best wishes
Jens



  reply	other threads:[~2017-01-22 13:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-07 11:43 message.el and mml-secure-bcc-is-safe Yuri D'Elia
2017-01-21 16:34 ` Lars Ingebrigtsen
2017-01-22 13:44   ` Jens Lechtenboerger [this message]
2017-01-25 17:02     ` Yuri D'Elia
2017-01-25 17:16       ` Lars Ingebrigtsen
2017-01-27 14:37         ` [PATCH] Run 'mml-secure-bcc-is-safe after 'message-send-hook Yuri D'Elia
2017-01-28 14:21           ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874m0rgqff.fsf@informationelle-selbstbestimmung-im-internet.de \
    --to=jens.lechtenboerger@fsfe.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=wavexx@thregr.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).