unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Koppelman <koppel@ece.lsu.edu>
Cc: ding@gnus.org
Subject: Re: `hard-newline' changes trigger format=flowed in Gnus
Date: Tue, 29 Nov 2005 15:10:00 -0600	[thread overview]
Message-ID: <7wwtirupnb.fsf@ece.lsu.edu> (raw)
In-Reply-To: <v94q5v9oga.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Tue, 29 Nov 2005 21:41:25 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> Hi,
>
> the changes related to `hard-newline' seem to provoke undesired
> behavior in Gnus.
[snip]
> 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.
[snip]
> I don't know if (and how) this bug should be fixed Gnus
> (`gnus/flow-fill.el' or `gnus/message.el'?) or in Emacs.

This problem is particularly insidious because the sender does not see
the flowed message, only the recipient who might not realize anything
is wrong.

  parent reply	other threads:[~2005-11-29 21: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 [this message]
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
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=7wwtirupnb.fsf@ece.lsu.edu \
    --to=koppel@ece.lsu.edu \
    --cc=ding@gnus.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).