Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Yuri D'Elia <wavexx@users.sf.net>
To: info-gnus-english@gnu.org
Subject: Re: Reply to self behavior
Date: Sun, 02 Jan 2011 13:52:59 +0100	[thread overview]
Message-ID: <87fwtbfowk.fsf@savara.sat.thregr.org> (raw)
In-Reply-To: <877henh6c8.fsf@lola.goethe.zz>

On Sun, 02 Jan 2011 12:51:03 +0100, David Kastrup wrote:
>> (setq fill-flowed-display-column nil)  (add-hook 'message-mode-hook
>> (lambda () (turn-off-auto-fill) (setq truncate-lines nil)
>> (use-hard-newlines)))  (add-hook 'gnus-article-mode-hook (lambda ()
>> (setq truncate-lines nil)))  My only complaint is that
>> use-hard-newlines' shouldn't be necessary.
>> Any line longer than `fill-flowed-encode-column' should trigger a
>> format=flowed message automatically instead of generating a warning.
>
> That's the worst comb quoting and unreadable run-in garbage I've seen in
> a long time.
>
> Impressive that you managed to create it using gnus.

I'm impressed, too :P

This is caused by (use-hard-newlines) actually. Since quoted and pasted
text has no 'hard' newlines, it gets unwrapped. This makes replies to
not-flowed messages substantially impossible.

I don't think that's really expected. I was thinking of manually adding
'hard' properties to newlines in `message-mode-hook', but I don't think
that would actually be sufficient.

A safer approach could be replacing all newlines with 'hard' newlines in
`message-send-hook' then setting `use-hard-newlines' manually to trick
Gnus into sending a flowed message.

Not fun.

  reply	other threads:[~2011-01-02 12:52 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2.1293039260.895.info-gnus-english@gnu.org>
2010-12-22 17:59 ` Adam Sjøgren
2010-12-22 18:54   ` Yuri D'Elia
2010-12-22 19:24     ` Tommy Kelly
2010-12-22 20:32       ` Yuri D'Elia
2010-12-22 21:18         ` Tommy Kelly
2010-12-22 21:46           ` Yuri D'Elia
     [not found]           ` <mailman.2.1293054423.1333.info-gnus-english@gnu.org>
2010-12-22 22:13             ` Adam Sjøgren
2010-12-24 16:58               ` Yuri D'Elia
     [not found]               ` <mailman.6.1293209898.7272.info-gnus-english@gnu.org>
2011-01-02  7:40                 ` Lars Magne Ingebrigtsen
2011-01-02 11:32                   ` Yuri D'Elia
2011-01-02 11:47                     ` Yuri D'Elia
     [not found]                   ` <mailman.0.1293967970.4418.info-gnus-english@gnu.org>
2011-01-02 11:51                     ` David Kastrup
2011-01-02 12:52                       ` Yuri D'Elia [this message]
2011-01-02 13:36                       ` Philipp Haselwarter
     [not found]                       ` <mailman.6.1293972797.4418.info-gnus-english@gnu.org>
2011-01-02 19:24                         ` Lars Magne Ingebrigtsen
2010-12-23  7:23         ` Reiner Steib
2010-12-23  9:24           ` Yuri D'Elia
2010-12-23 19:13             ` Reiner Steib
2010-12-23 11:03           ` Richard Riley
     [not found]       ` <mailman.0.1293049947.1333.info-gnus-english@gnu.org>
2010-12-22 21:37         ` Karl Kleinpaste
2010-12-23  2:50           ` Dan Christensen
     [not found]   ` <mailman.5.1293044090.895.info-gnus-english@gnu.org>
2010-12-22 19:48     ` Adam Sjøgren
2010-12-22 17:34 Yuri D'Elia

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

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

  git send-email \
    --in-reply-to=87fwtbfowk.fsf@savara.sat.thregr.org \
    --to=wavexx@users.sf.net \
    --cc=info-gnus-english@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.
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 NNTP newsgroup(s).