Re: [PATCH] message-goto-body after <#secure

["Łukasz Stelmach" <lukasz.stelmach@iem.pw.edu.pl>]

Julien Danjou <julien@danjou.info> writes:

> <#secure method=pgpmime mode=sign>
> On Wed, Nov 24 2010, Lars Magne Ingebrigtsen wrote:
>
>> Actually, I think this is probably the wrong way to do it.  If you want
>> to insert <#secure automatically in all your message buffers, you should
>> do it after everything is inserted, and not before yanking.
[...]
> ;; plug this into message-setup-hook
> (add-hook 'gnus-message-setup-hook 'jd:gnus-secure-message-sign)

Every day I learn something new: message-setup-hook and
gnus-message-setup-hook are quite different ones. And there is no
base64 citation problem if I put mml-secure-message-sign-pgpmime in the
latter one. However, I still think C-c C-b should place cursor after
the <#secure tag. What I did wrong is that I forgot to return the
current position from the message-goto-body.

[Here was a patch that does not work either]

It seems that the it won't work one way or the other. Even If I return
(point) from the message-goto-body and "base64 citation" works ok then
mml decoding breaks (hence the unused <#secure > tag in
<87vd3mba16.fsf@kotik.lan>).

I give up (but I still would like C-c C-b to beam me up to the right
point)

-- 
Miłego dnia,
Łukasz Stelmach