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 pdmef):
Replying to [comment:10 idallen]:
> If mutt were following standards by enforcing the line-length "SHOULD"
> clause of the RFC, mutt SHOULD not permit *any* lines in the entire
> message to be longer than 78. The RFC 78-character-limit recommendation
> doesn't apply only to the header lines; it applies to *all* the lines
> in the message, including the message body lines.
Mutt doesn't follow standards by enforcing things regarding line lengths:
it tries to respect them where it reasonably can. 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).
Any client should be liberal what they accept but strict in what they
sent.
> Mutt MUST let me generate long header lines, for two reasons:
> 1. Since mutt lets me write long body lines, it must also let me write
long header lines, if I ask for it. They are both covered by the same
RFC.
Just because one doesn't/can't follow common practice in particular places
doesn't mean you can/should/must completely ignore it.
> 2. 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.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3135#comment:11>
Mutt <http://www.mutt.org/>
The Mutt mail user agent