On 07Sep2015 00:31, Grady Martin <sunnycemet...@gmail.com> wrote:
On 2015年09月07日 13時39分, Cameron Simpson wrote:
Hmm. I was going to complain about your reflow_*
settings (even though the defaults are to reflow
at 78 columns), but I see that they are not
properly obeyed for me either. Grady's message
wraps at my terminal width, even though I have
just set reflow_wrap to 40 as a test.

The reflow_wrap setting does not seem to affect messages for me, either, 
despite reflow_text being set.  This could be a problem, as the ideal display 
width of lines is a matter of personal opinion, and people's opinions differ.  
Personally, I do not like wasted screen space and have set reflow_wrap to 0.  
The problem is that Patrick, for example, would probably like a reflow_wrap 
value of 80 and yet setting it to 80 does nothing.

I've just been rereading RFC3676, which specifies the format=flowed format. It has these juicy statements in section 4.1:

If the line ends in a space, the line is flowed. Otherwise it is fixed.

and:

A series of one or more flowed lines followed by one fixed line is considered a paragraph, and MAY be flowed (wrapped and unwrapped) as appropriate on display and in the construction of new messages (see Section 4.5).

The salient difference between my messages (which reflow to the reflow_wrap value) and yours (which do not, and are simply folded at the display width) is that your messages have every paragraph as a single line. By the above definitions, that is a fixed line which should not be reflowed.

What you need to do is edit in a mode that produces flowed paragraphs. I'm using a slightly annoying vim setting that does most of this, and compose messages with "set editor=vim-flowed", where vim-flowed is this:

 https://bitbucket.org/cameron_simpson/css/src/tip/bin/vim-flowed

The upshot is that my paragraphs _are_ multiline, with trailing spaces. And thus get reflowed.

Yours are "fixed", and mutt (correctly) tries to not reflow them. (As you might wish it to with code snippets or CSV file lines etc.)

Cheers,
Cameron Simpson <c...@zip.com.au>

Reply via email to