[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mhbuild and long header fields
From: |
Philipp |
Subject: |
Re: mhbuild and long header fields |
Date: |
Sun, 17 Sep 2023 18:37:41 +0200 |
[2023-09-16 12:36] David Levine <levinedl@acm.org>
> Phillipp, I've been using your header field folding for a few weeks and I
> really like it. I think that it should be committed, it's big step forward.
Good to hear. Do you want a format-patch of the final version?
> One issue to resolve first: the References header field at the end of this
> message ends with:
> <16f13de3df80f62de768420a3cc3a2fe.philipp@bureaucracy.de>
> <14298-1693614066.188834@mIBq.BRD6.6M0V>
>
> There's always an extra space in front of the Message-ID that was appended
> last. Is that a relic of repl?
That's strange and I can't reproduce this. Also I can't find code which
would explain this in repl and the default configuration. Maybe in the
convert interface of mhbuild?
> Or, should the folding code collapse multiple white space characters at the
> beginning of a line?
No, fold() should not change the body of the field. Depending on the
context multible white space characters might have a meaning or are used
to increase readability without a MUA.
Philipp
- Re: mhbuild and long header fields, Philipp, 2023/09/01
- Re: mhbuild and long header fields, David Levine, 2023/09/01
- Re: mhbuild and long header fields, David Levine, 2023/09/16
- Re: mhbuild and long header fields,
Philipp <=
- Re: mhbuild and long header fields, David Levine, 2023/09/17
- Re: mhbuild and long header fields, Philipp Takacs, 2023/09/17
- Re: mhbuild and long header fields, David Levine, 2023/09/17
- Re: mhbuild and long header fields, Philipp, 2023/09/18
- Re: mhbuild and long header fields, Andy Bradford, 2023/09/18
- Message not available
- Re: mhbuild and long header fields, David Levine, 2023/09/18