Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: gnus-narrow-to-head, message-narrow-to-body?
Date: Mon, 07 Apr 2003 18:33:35 +0200	[thread overview]
Message-ID: <v94r5a5ktc.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3u1dapdv5.fsf@avarre.com>

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.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  parent reply	other threads:[~2003-04-07 16:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 13:55 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 [this message]
2003-04-07 22:36       ` secure method (was: gnus-narrow-to-head, message-narrow-to-body?) Julien Avarre
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=v94r5a5ktc.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).