From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: letting split rules have access to the message body...
Date: 15 May 2001 11:24:20 +0200 [thread overview]
Message-ID: <vafzocfrmm3.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87k83jk4sx.fsf@mclinux.com> (Josh Huber's message of "14 May 2001 17:18:38 -0400")
On 14 May 2001, Josh Huber wrote:
> Is it possible (for example) to narrow to the body of the already
> narrowed region, and somehow widen to the previously narrowed
> region? something like pop-narrow? :)
I'm sure that
(save-restriction
...narrow to headers...)
(save-restriction
...narrow to body...)
does the right thing: after the first save-restriction returns, the
previous narrowing is in effect. save-restriction is like let for
narrowing boundaries.
kai
--
The passive voice should never be used.
next prev parent reply other threads:[~2001-05-15 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 21:30 Josh Huber
2001-05-11 13:20 ` Josh Huber
2001-05-11 22:50 ` Kai Großjohann
2001-05-14 19:13 ` Josh Huber
2001-05-14 20:16 ` Kai Großjohann
2001-05-14 21:18 ` Josh Huber
2001-05-15 9:24 ` Kai Großjohann [this message]
2001-05-15 16:33 ` Josh Huber
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=vafzocfrmm3.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).