<<< Date Index >>>     <<< Thread Index >>>

Re: [Mutt] #3001: format=flowed (interoperability) (was:



#3001: format=flowed (interoperability)
--------------------------+-------------------------------------------------
  Reporter:  js           |       Owner:  pdmef              
      Type:  enhancement  |      Status:  new                
  Priority:  minor        |   Milestone:  1.6                
 Component:  mutt         |     Version:                     
Resolution:               |    Keywords:  format=flowed patch
--------------------------+-------------------------------------------------

Comment(by pdmef):

 Update/summary to make deciding easier.

 Issue 1 is interoperability. The ff.diff patch adds $flowed_compat. The
 changes are:

   * when making format=flowed  replies to format=fixed messages, trailing
 spaces are trimmed: this is to make sure that when you make an f=f reply
 you suddenly don't produce flowable paragraphs because the format=fixed
 original mail had some trailing spaces.
   * when making format=fixed replies to format=flowed messages,
 $indent_string should be used since it's still a format=fixed message. And
 as you may then quote flowed paragraphs with a possibly non-f=f compatible
 $indent_string (as is the default), it wouldn't be valid f=f anymore if
 somebody made an f=f reply on your message again; as a result, we also
 trim spaces when making a fixed reply to a flowed message.

 Issue 2 is an objection by TLR about the new f=f handler. Quote in
 20080118120119.GA28830@xxxxxxxxxxxxxxxxxxxxxxxxxxx:

 {{{
 the current behavior of joining lines with format=flowed just
 because mutt can (and has enough screen real estate) is annoying and
 unergonomic (best reading speed for plain text occurs around 50-60
 characters, not 150!).  Please revert the default behavior to the
 old one (joining lines only if we had to wrap them before), and make
 the new behavior optional.

 As an alternative, make the display width of flowed lines
 configurable.
 }}}

 For issue 1 I think we should add the patch, maybe even without an option.
 As we claim to support f=f, mutt should be aware of the drawbacks and
 implications non-f=f compatible clients introduce.

 For issue 2 I (now) agree with TLR and suggest to only enable (the
 current) flowing if $text_flowed is set. If unset, we assume incomming f=f
 text is sanely formatted and suitable for display. If not and one of the
 lines is too long we'd flow the paragraph. That would leave us only with
 ugly formatting with all lines shorter than $wrap... which is kind of an
 edge case anyway. The current behaviour can then be achieved by a message-
 hook setting text_flowed and a send-hook unsetting it.

-- 
Ticket URL: <http://dev.mutt.org/trac/ticket/3001#comment:4>
Mutt <http://www.mutt.org/>
The Mutt mail user agent