On Sun, Dec 20, 2020 at 01:08:58PM -0800, Kevin J. McCarthy wrote: > On Sun, Dec 20, 2020 at 08:22:46PM +0100, Josef Wolf wrote: > > On Fri, Dec 18, 2020 at 11:51:56AM -0800, Kevin J. McCarthy wrote: > > > On Fri, Dec 18, 2020 at 11:16:23AM +0100, Josef Wolf wrote: > > > > > * Try to <pipe-message> to less. > > > > This shows the whole message, includug body. > > This, along with the ability to see (and act on) attachments in the > <view-attachments> menu, hints that Mutt isn't completely confused. I'm > starting to suspect some kind of configuration issue.
Hmmm. I have not changed the config for years. But the timestamp of /etc/Muttrc is 30.11.2020. Looks like the distro might have changed something on the last upgrade.. > What happens if you ":set pipe_decode" and then retry <pipe-message> to > less? Now less won't show the body anymore. > Do you have any hooks, macros, or such that might be altering settings after > you perform a particular action? Perhaps auto_view settings, > $honor_disposition, $display_filter? I have auto_view text/html application/x-gunzip application/x-gzip application/ms-tnef but unauto_view those values don't help. Changing those other values don't help either. > Is there anything new in your mailcap files for text/plain? ~/.mailcap has noch changed since 2018 and contains only: application/ms-tnef; tnef -w %s No system-wiede mailcap around here. > It feels like the rendering of the output in the display is going through a > program which is failing. But how comes that this external program fails for one instance of mutt but works fine on a freshly started instance of mutt? -- Josef Wolf j...@raven.inka.de
