From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/57397 Path: main.gmane.org!not-for-mail From: Karl Chen Newsgroups: gmane.emacs.gnus.general Subject: Re: M-q in headers Date: Sun, 16 May 2004 18:57:55 -0700 Sender: ding-owner@lists.math.uh.edu Message-ID: References: <87fzctdjsz.fsf@emptyhost.emptydomain.de> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084768857 11991 80.91.224.253 (17 May 2004 04:40:57 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 May 2004 04:40:57 +0000 (UTC) Original-X-From: ding-owner+M5937@lists.math.uh.edu Mon May 17 06:40:49 2004 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BPZvl-0001wl-00 for ; Mon, 17 May 2004 06:40:49 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 1BPZv9-0000eZ-00; Sun, 16 May 2004 23:40:11 -0500 Original-Received: from util2.math.uh.edu ([129.7.128.23]) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 1BPZJ6-0000SN-00 for ding@lists.math.uh.edu; Sun, 16 May 2004 23:00:52 -0500 Original-Received: from justine.libertine.org ([66.139.78.221] ident=postfix) by util2.math.uh.edu with esmtp (Exim 4.30) id 1BPZJ5-00020w-GM for ding@lists.math.uh.edu; Sun, 16 May 2004 23:00:51 -0500 Original-Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by justine.libertine.org (Postfix) with ESMTP id 133D83A01F6 for ; Sun, 16 May 2004 23:00:50 -0500 (CDT) Original-Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BPZJ2-0004cn-00 for ; Mon, 17 May 2004 06:00:48 +0200 Original-Received: from hkn.eecs.berkeley.edu ([128.32.47.228]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 May 2004 06:00:48 +0200 Original-Received: from quarl+dated+1085190466.0ac2e2 by hkn.eecs.berkeley.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 17 May 2004 06:00:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: ding@gnus.org Original-Lines: 72 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: hkn.eecs.berkeley.edu X-Quack-Archive: 1 User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:dJItMa+psoSwUpr0ImIDUzErgeU= Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:57397 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:57397 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 writes: Lars> Lars> Kai Grossjohann 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