From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: what is different between a message "head" and "headers"?
Date: 01 Dec 1999 20:55:30 +0100 [thread overview]
Message-ID: <m3aenuzb9p.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m2d7t0s799.fsf@swift.shore.net>
Matt Swift <swift@alum.mit.edu> writes:
> message.el has `message-narrow-to-head', `message-narrow-to-headers',
> and `message-narrow-to-head-or-headers'.
>
> I can read the code, I want to know what the coneptual differnce is.
> All this from the manual only seems to suggest that head and headers
> are being used in yet one more way than is explained here:
In the Message context, there's not much of a concept. I just needed
to be able to narrow to the bit over the "text follows this line" line
in some instances, and in other instances I needed to narrow to the
bit over the first blank line.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-12-01 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 7:01 Matt Swift
1999-12-01 19:55 ` Lars Magne Ingebrigtsen [this message]
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=m3aenuzb9p.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).