Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: "Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>
Cc: ding@gnus.org
Subject: Re: [PATCH] message-goto-body after <#secure
Date: Wed, 24 Nov 2010 18:28:55 +0100	[thread overview]
Message-ID: <877hg2wrzc.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <87fwurlpyw.fsf@kotik.lan> (=?utf-8?Q?=22=C5=81ukasz?= Stelmach"'s message of "Tue, 23 Nov 2010 21:55:35 +0100")

On Tue, Nov 23 2010, Łukasz Stelmach wrote:

> The following patch makes message-goto-body function put cursor after
> possible "<#secure" tag. This hits two birds with one stone: pressing
> C-c C-b moves me where I can start typing and any citations that get
> inserted into a new message buffer when replying (I have not tested
> resending or forwarding yet but I suppose it works the same way) leave
> the tag at the very begining of a message.
>
> Why I wrote this? I've set up mml-secure-message-sign-pgpmime as a part
> of message-setup-hook. I prefere this to putting it in message-send-hook
> because I can decide whether to sign a message or not. And it works well
> for a new message. However, it fails for replies because just before
> citations are inserted message-goto-body sets point *brefore*
> the <#secure tag that is there since message-setup-hook gets fired
> before citations.

Thanks, pushed.

Cheers,
-- 
Julien Danjou
// ᐰ <julien@danjou.info>   http://julien.danjou.info



  reply	other threads:[~2010-11-24 17:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-23 20:55 Łukasz Stelmach
2010-11-24 17:28 ` Julien Danjou [this message]
2010-11-24 20:53 ` Lars Magne Ingebrigtsen
2010-11-24 21:20   ` Julien Danjou
2010-11-24 23:16     ` Łukasz Stelmach
2010-11-24 23:19       ` Lars Magne 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

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

  git send-email \
    --in-reply-to=877hg2wrzc.fsf@keller.adm.naquadah.org \
    --to=julien@danjou.info \
    --cc=ding@gnus.org \
    --cc=lukasz.stelmach@iem.pw.edu.pl \
    /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).