Hi Klemens, Klemens Nanni wrote on Wed, Jul 05, 2017 at 05:44:42PM +0200: > On Wed, Jul 05, 2017 at 05:27:18PM +0200, Ingo Schwarze wrote:
>> No need to fix it because the patch is not likely to go anywhere, >> but once again you mangled the patch such that it won't even apply. > Hm, the diff taken from my mail as is applies cleanly here. Oops, i'd like to offer half an apology. Your diff was fine, but your mail headers contain a specification that prevents correct display, which mislead me. I had never seen such misformatting in mutt(1) before. The problem is here: > Content-Type: text/plain; charset=us-ascii; format=flowed Please disable the "format=flowed". Patches are not flowed content. At least mutt(1) does weird stuff by default and screws up the display when finding that header, and other mail clients might be worse. I found the problem by reading part of /usr/ports/pobj/mutt-1.8.3/mutt-1.8.3/pager.c Now, how do i get the vomit out of my keyboard. Apparently, even mutt(1) is bloatware nowadays. Of course, i also fixed my .muttrc settings to not change the formatting of the mails i'm trying to read. Adding "unset reflow_text" to .muttrc fixes the screwup. What a bother that such insane features are enabled by default and send you on a wild goose chase to the docomentation (and even to the source code) before you can use the mail client. What the hell, who wants his mail client to lie to them about the contents of mail they receive? Unfortunately, mutt is the only usable mail client i have ever seen after elm and pine died (and it was always better than pine in the first place). So no choice here... :-( Enough ranted, back to work now. :) Yours, Ingo
