Hi Ingo, off-topic but important.
In article <20170705164444.ga82...@athene.usta.de> you wrote: > 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 > > This is exactly why I started to think about adding some features to mailx. I wrote the mime encoder I posted in misc@ (I mentioned you about it in the ksh utf8 thread) that led me more late to the utf8 parser. It was mostly a C student exercise, I'm still not able to do a proper patch, but I posted it anyway to check if someone else thought about that. I started with the encoder but after thinking it twice I realized that's not the better move. The clever move would be to add mailx an option to let the user add-modify *any* header. Just adding that only one feature you can solve the rest piping commands or your own shell scripts. I think netbsd mailx already has this feature. Perhaps someone more skilled than me (I'm still green to do it) could borrow the code from there.
