From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Koppelman Newsgroups: gmane.emacs.devel,gmane.emacs.gnus.general Subject: Re: `hard-newline' changes trigger format=flowed in Gnus Date: Wed, 30 Nov 2005 14:31:47 -0600 Message-ID: <7wlkz5ho7g.fsf@ece.lsu.edu> References: <87k6er6m9l.fsf@stupidchicken.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1133382947 16081 80.91.229.2 (30 Nov 2005 20:35:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 30 Nov 2005 20:35:47 +0000 (UTC) Cc: ding@gnus.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 30 21:35:39 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EhYce-0002lk-9s for ged-emacs-devel@m.gmane.org; Wed, 30 Nov 2005 21:32:12 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EhYcc-0002fq-U6 for ged-emacs-devel@m.gmane.org; Wed, 30 Nov 2005 15:32:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EhYcU-0002fk-Ky for emacs-devel@gnu.org; Wed, 30 Nov 2005 15:32:02 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EhYcT-0002fV-1a for emacs-devel@gnu.org; Wed, 30 Nov 2005 15:32:02 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EhYcS-0002fS-UG for emacs-devel@gnu.org; Wed, 30 Nov 2005 15:32:00 -0500 Original-Received: from [130.39.223.71] (helo=ece.lsu.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EhYcS-0004EV-Pb for emacs-devel@gnu.org; Wed, 30 Nov 2005 15:32:01 -0500 Original-Received: from nested.ece.lsu.edu (nested [130.39.222.143]) by ece.lsu.edu (8.11.7p1+Sun/8.11.7) with ESMTP id jAUKVGw22639; Wed, 30 Nov 2005 14:31:16 -0600 (CST) Original-Received: from nested.ece.lsu.edu (localhost [127.0.0.1]) by nested.ece.lsu.edu (8.12.11/8.13.1) with ESMTP id jAUKVmrQ016052; Wed, 30 Nov 2005 14:31:48 -0600 Original-Received: (from koppel@localhost) by nested.ece.lsu.edu (8.12.11/8.12.11/Submit) id jAUKVlA6016050; Wed, 30 Nov 2005 14:31:47 -0600 Original-To: Emacs development In-Reply-To: (Reiner Steib's message of "Wed, 30 Nov 2005 16:10:28 +0100") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:46830 gmane.emacs.gnus.general:61442 Archived-At: Reiner Steib writes: > There is some information in emacs-mime.texi: > > ,----[ (info "(emacs-mime)Flowed text") ] > | The Emacs MIME library will respect the `use-hard-newlines' variable > | (*note Hard and Soft Newlines: (emacs)Hard and Soft Newlines.) when > | encoding a message, and the "format=flowed" Content-Type parameter when > | decoding a message. > | > | On encoding text, regardless of `use-hard-newlines', lines > | terminated by soft newline characters are filled together and wrapped > | after the column decided by `fill-flowed-encode-column'. Quotation > | marks (matching `^>* ?') are respected. The variable controls how the > | text will look in a client that does not support flowed text, the > | default is to wrap after 66 characters. If hard newline characters are > | not present in the buffer, no flow encoding occurs. > | [...] > `---- > > IMHO, it won't hurt to add a short note and reference to this > explanation in gnus.texi and message.texi. The only occurrence is in > the "New Features" section (info "(gnus)Oort Gnus"). Suggestions? If I understand things correctly if soft and hard newline characters are found then it will be assumed that a soft newline is what was intended and so text will be flowed, no questions asked. But there are many cases in which the soft newline character is there by "accident". The sender won't know until the recipient gets back to the sender and then the sender will have to delve deeply into lisp or the documentation to diagnose the problem and develop a workaround. Therefore one must be much more careful before flowing. Perhaps some combination of the following: Some indication that text will be assumed flowable, perhaps in the modeline or perhaps by highlighting around the soft newlines. If flowability has been assumed then ask the user if that's correct and take yes, yes always, no, and no never responses.