unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Emacs development <emacs-devel@gnu.org>, <ding@gnus.org>
Subject: Re: `hard-newline' changes trigger format=flowed in Gnus
Date: Wed, 30 Nov 2005 16:10:28 +0100	[thread overview]
Message-ID: <v98xv6masb.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <87k6er6m9l.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 29 Nov 2005 18:56:54 -0500")

On Tue, Nov 29 2005, Chong Yidong wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> When copying some lines from the mail header (in Gnus' message mode)
>> into the mail body, some of the newlines seem to be marked as `hard'.
>> When sending (or previewing) the message, the function
>> `fill-flowed-encode' detects the hard newlines and the whole message
>> is encodes as format=flowed which leads to an unexpected output.
>
> What is the intended purpose of fill-flowed-encode?  What is the
> reason for message-mode to do anything special when there are hard
> newlines in the buffer?

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?


On Wed, Nov 30 2005, Chong Yidong wrote:

> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> the changes related to `hard-newline' seem to provoke undesired
>> behavior in Gnus.
>
> I found out that it's not necessary to use hard-newline in those
> places after all.  I've reverted the 2005-11-29 changes to
> mailheader.el

Thanks.  AFAICS this fixed the problem.

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



  reply	other threads:[~2005-11-30 15:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 20:41 `hard-newline' changes trigger format=flowed in Gnus Reiner Steib
2005-11-29 21:08 ` Romain Francoise
2005-11-29 21:10 ` David Koppelman
2005-11-29 22:18 ` Chong Yidong
2005-11-30 13:35   ` Per Abrahamsen
2005-11-29 23:56 ` Chong Yidong
2005-11-30 15:10   ` Reiner Steib [this message]
2005-11-30 16:30     ` Sam Steingold
2005-11-30 20:23       ` Reiner Steib
2005-11-30 22:17         ` Sam Steingold
2005-12-01 17:48           ` Reiner Steib
2005-11-30 20:31     ` David Koppelman
2005-12-01 17:44       ` Reiner Steib

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=v98xv6masb.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).