From: Karl Chen <quarl+dated+1085190466.0ac2e2@nospam.quarl.org>
Subject: Re: M-q in headers
Date: Sun, 16 May 2004 18:57:55 -0700 [thread overview]
Message-ID: <quack.20040516T1857.j5n0474xy4@hkn.eecs.berkeley.edu> (raw)
In-Reply-To: <m3oeoob93l.fsf@quimbies.gnus.org>
All standard RFC2822 headers can be folded (filled). Other
headers should probably be left alone. This could be implemented
with a list/regexp of fillable headers. I recommend " " as the
fill prefix. It should work well with auto-fill-mode. It should
try to work well with existing third-party extensions like
bbdb-autowrap-recipient.
http://www.faqs.org/rfcs/rfc2822.html:
2.2.3. Long Header Fields
Each header field is logically a single line of characters comprising
the field name, the colon, and the field body. For convenience
however, and to deal with the 998/78 character limitations per line,
the field body portion of a header field can be split into a multiple
line representation; this is called "folding". The general rule is
that wherever this standard allows for folding white space (not
simply WSP characters), a CRLF may be inserted before any WSP. For
example, the header field:
Subject: This is a test
can be represented as:
Subject: This
is a test
Note: Though structured field bodies are defined in such a way that
folding can take place between many of the lexical tokens (and even
within some of the lexical tokens), folding SHOULD be limited to
placing the CRLF at higher-level syntactic breaks. For instance, if
a field body is defined as comma-separated values, it is recommended
that folding occur after the comma separating the structured items in
preference to other places where the field could be folded, even if
it is allowed elsewhere.
The process of moving from this folded multiple-line representation
of a header field to its single line representation is called
"unfolding". Unfolding is accomplished by simply removing any CRLF
that is immediately followed by WSP. Each header field should be
treated in its unfolded form for further syntactic and semantic
evaluation.
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars>
Lars> Kai Grossjohann <kai@emptydomain.de> writes:
>> WIBNI M-q in a header would refill that header?
Lars>
Lars> Wow. `M-q' in Message headers is really broken... I've
Lars> never noticed before. What's the correct way to fix
Lars> that? Some headers really aren't refillable (for
Lars> instance, "Face"), but some are (like "From").
--
Karl 2004-05-16 18:47
next prev parent reply other threads:[~2004-05-17 1:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 8:59 Kai Grossjohann
2004-03-01 20:23 ` Reiner Steib
2004-05-16 17:00 ` Lars Magne Ingebrigtsen
2004-05-17 1:57 ` Karl Chen [this message]
2004-05-17 12:18 ` Lars Magne Ingebrigtsen
2004-05-17 21:42 ` Danny Siu
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=quack.20040516T1857.j5n0474xy4@hkn.eecs.berkeley.edu \
--to=quarl+dated+1085190466.0ac2e2@nospam.quarl.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).