message.el bug: message-field-value issue with folded headers

message.el bug: message-field-value issue with folded headers

[Yuri D'Elia]

In a recent change in message.el the headers are folded automatically
before being sent.

If the header has no whitespace, it will essentially move the entire
value into the next line:

|Header:
| long-value

Does it make sense to do so?

Anyway, `message-fetch-field' doesn't handle this case correctly. By
substituting "\n[\t ]+" => " " we're left with a leading space:

  " long value"

Can we strip leading and trailing whitespace from value at the end of
the function?

Re: message.el bug: message-field-value issue with folded headers

[Lars Ingebrigtsen]

Yuri D'Elia <wavexx@thregr.org> writes:

> If the header has no whitespace, it will essentially move the entire
> value into the next line:
>
> |Header:
> | long-value
>
> Does it make sense to do so?

Nope; that's a bug.

> Anyway, `message-fetch-field' doesn't handle this case correctly. By
> substituting "\n[\t ]+" => " " we're left with a leading space:
>
>   " long value"

That's also a bug.  It's nice that this folding change is revealing so
many bugs.  :-)

I'll get fixing.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Re: message.el bug: message-field-value issue with folded headers

[Lars Ingebrigtsen]

Lars Ingebrigtsen <larsi@gnus.org> writes:

> I'll get fixing.

Both these should now be fixed on the trunk.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no