info-gnus-english
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reply to self behavior


From: David Kastrup
Subject: Re: Reply to self behavior
Date: Sun, 02 Jan 2011 12:51:03 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux)

Yuri D'Elia <wavexx@users.sf.net> writes:

> On Sun, 02 Jan 2011 08:40:33 +0100, Lars Magne Ingebrigtsen wrote: 
>> Yuri D'Elia <wavexx@users.sf.net> writes: > >>>> (_real_ 
> format=flowed support anyone? it's supported since 199? in >>>>
> outlook) >>> >>> What doesn't work? And what is format=flowed? Why
> would you want it?  >> >> format=flowed encodes hard-newlines in the
> message, while still wrapping >> the source of the message to 80
> columns. This allow compliant readers to >> either show the wrapped
> text or flow the content to the window's >> margins.  > > In what way
> doesn't format=flowed work in Gnus?  I think that was 
>> implemented at least a decade ago, but it may have bitrotted in 
> the mean > time...  
>
> After reading the sources, I was able to achieve flowed zenity with
> the following:
>
> (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.

-- 
David Kastrup


reply via email to

[Prev in Thread] Current Thread [Next in Thread]