Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Avarre <julien@avarre.com>
Subject: secure method (was: gnus-narrow-to-head, message-narrow-to-body?)
Date: Tue, 08 Apr 2003 00:36:13 +0200	[thread overview]
Message-ID: <m3he9aorz6.fsf_-_@avarre.com> (raw)
In-Reply-To: <v94r5a5ktc.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 07 Apr 2003 18:33:35 +0200")

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


Reiner Steib <4.uce.03.r.s@nurfuerspam.de> disait récemment  :

> On Mon, Apr 07 2003, Julien Avarre wrote:
> 
> > kai.grossjohann@gmx.net (Kai Großjohann) disait récemment  :
> >
> >> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> >> 
> >> > What about `gnus-narrow-to-head' and `message-narrow-to-body'?
> >> 
> >> Are they needed?
> 
> I though that `message-narrow-to-body' would simplify the use of
> `latin-unity-remap-region' or `latin-unity-sanity-check' on the
> message body.  See the discussion on XEmacs+`latin-unity' in dcsg.
> 
> But as we can see, it might be useful in other places too:
> 
> > They can be usesul for the pattern [...]  Which is not very
> > practical.  Reiner's functions should help us for moving the pgg
> > pattern at the right place, am I right ?
> 
> I don't have an example for `gnus-narrow-to-head' at hand, but maybe
> it should be added for completeness.
> 
> Bye, Reiner.

Sorry, I've  probably misunderstood this thread. But  I still continue
to ask my question :-) 

Actually, I've put in my .gnus file :


   (add-hook 'message-setup-hook 'mml-secure-message-sign-pgpmime)


It allows me to automatically put the pattern in my message :

                  <#secure method=pgpmime mode=sign>

But when I reply  to a message, this pattern is written  at the end of
quoted text.  Gnus do not interpret  it. I have to move it manually to
the beginning of the body :-(

Is there a way to avoid that, automatize this ?

Thanks'

-- 
Julien ``Eole'' Avarre
julien at avarre dot com

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

  reply	other threads:[~2003-04-07 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 13:55 gnus-narrow-to-head, message-narrow-to-body? Reiner Steib
2003-04-07 14:27 ` Kai Großjohann
2003-04-07 14:43   ` Julien Avarre
2003-04-07 15:59     ` Kai Großjohann
2003-04-07 16:33     ` Reiner Steib
2003-04-07 22:36       ` Julien Avarre [this message]
2003-04-07 22:58         ` secure method Vasily Korytov
2003-04-08  0:01           ` Julien Avarre
2003-04-08  0:08             ` Julien Avarre

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=m3he9aorz6.fsf_-_@avarre.com \
    --to=julien@avarre.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).