Re: [Mutt] #3135: cannot stop header wrap/folding;
#3135: cannot stop header wrap/folding; wrapping ignores user $wrap setting
----------------------+-----------------------------------------------------
Reporter: idallen | Owner: pdmef
Type: defect | Status: started
Priority: minor | Milestone: 1.6
Component: mutt | Version: 1.5.18
Resolution: | Keywords: wrap header fold folding terminal width
----------------------+-----------------------------------------------------
Comment(by idallen):
| Mutt doesn't follow standards by enforcing things regarding line
lengths:
| it tries to respect them where it reasonably can.
The standard doesn't *require* a line length of 78, it "RECOMMENDS"
it. I (the user, not the program) should be able to over-ride that
recommendation if I want. That's what "SHOULD" and "RECOMMEND" mean.
| Wrapping text after the user has finished editing it is not a
| reasonable thing to do (signatures, ascii-art, etc, the user knows his
| text better than mutt).
Wrapping *anything* against the user's will is not reasonable, even
headers. The user also knows his headers better than mutt. The 78 number
on line length is a "SHOULD", not a "MUST". The only line length standard
mutt "MUST" enforce is the 998 limit. Let the user, not the program,
decide the line and header length provided it's less than 998.
| Any client should be liberal what they accept but strict in what they
sent.
| Just because one doesn't/can't follow common practice in particular
| places doesn't mean you can/should/must completely ignore it.
So make the default be strict and wrap at 78; that's good. But, if I want
to turn wrap at 78 off, the RFC allows that and you must let me do it.
1. Mutt has no authority to treat RFC "SHOULD" clauses as "MUST" clauses.
| It doesn't do that. If it would, it would also break (for example)
| Message-IDs that are too long. Instead it leaves them intact because
| its aware of the consequences that this likely breaks threading. So it
| has valid reasons to not follow the standard in such a case.
Mutt should not be trying to be smarter than I am, if I ask not to wrap
at 78. In the case of "SHOULD" and "RECOMMENDS" it is the user, not the
program, that should decide whether or not to obey the rule. Only in
the case of "MUST" should the program over-ride what the user wants.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3135#comment:12>
Mutt <http://www.mutt.org/>
The Mutt mail user agent