#3673: when $edit_headers is set, mutt mangles first-line URLs in the message
body.
-------------------------+----------------------
Reporter: balderdash | Owner: mutt-dev
Type: defect | Status: new
Priority: major | Milestone:
Component: mutt | Version: 1.5.22
Resolution: | Keywords:
-------------------------+----------------------
Comment (by kevin8t8):
Sinan's response already put this much more eloquently, but just to
summarize/repeat:
balderdash wrote:
> It's mutt's job to transform what's in the editor into the finished
> product, or a piece of the finished product, and so it's mutt's job to
> insert the blank line if necessary.
It *will* properly separate the headers from the body *if* it can properly
detect the end of the headers.
The code which parses the headers out, mutt_read_rfc822_header(), is used
in many places in mutt, and recognizes headers without a trailing space,
e.g. "Foo:bar", or even just "Foo:". The space is not actually required
by the RFC, so your suggestion is not feasible.
If you are going to use $edit_headers, and especially if your first line
follows the valid syntax of a header, prudence would dictate keeping the
blank line between the headers and body. Mutt already does the best it
can at separating the headers out.
Sinan, your documentation update looks worth sending to the list as a
patch. It doesn't seem to be explicitly mentioned in the manual to keep
the blank line.
--
Ticket URL: <http://dev.mutt.org/trac/ticket/3673#comment:6>
Mutt <http://www.mutt.org/>
The Mutt mail user agent
