M-q in headers

M-q in headers

[Kai Grossjohann]

WIBNI M-q in a header would refill that header?

Kai

Re: M-q in headers

[Reiner Steib]

On Mon, Mar 01 2004, Kai Grossjohann wrote:

> WIBNI M-q in a header would refill that header?

Sure.

I often find myself typing `M-q' in the headers destroying everything.
Luckily, I'm aware of `C-/'...

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/

Re: M-q in headers

[Lars Magne Ingebrigtsen]

Kai Grossjohann <kai@emptydomain.de> writes:

> WIBNI M-q in a header would refill that header?

Wow.  `M-q' in Message headers is really broken...  I've never
noticed before.  What's the correct way to fix that?  Some headers
really aren't refillable (for instance, "Face"), but some are (like
"From"). 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: M-q in headers

[Karl Chen]

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

Re: M-q in headers

[Lars Magne Ingebrigtsen]

Karl Chen <quarl+dated+1085190466.0ac2e2@nospam.quarl.org> writes:

> 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've now implemented this.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: M-q in headers

[Danny Siu]

Thanks Lars!  It works like charm.

I have been waiting for M-q to work in some decent fashion for the longest
time!

Lars Magne Ingebrigtsen writes:

  Lars> Karl Chen <quarl+dated+1085190466.0ac2e2@nospam.quarl.org> writes:
  >> 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.

  Lars> I've now implemented this.

  Lars> -- (domestic pets only, the antidote for overdose, milk.)
  Lars>   larsi@gnus.org * Lars Magne Ingebrigtsen

-- 
Danny Dick-Fung Siu              mailto:dsiu@adobe.com
Advanced Technology Group @ Adobe Systems Incorporated