unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Al Haji-Ali <abdo.haji.ali@gmail.com>, notmuch@notmuchmail.org
Subject: Re: Overriding mm-inline-override-types in notmuch-show
Date: Wed, 27 Jul 2022 13:26:44 -0300	[thread overview]
Message-ID: <87bktaa5dn.fsf@tethera.net> (raw)
In-Reply-To: <877d41nmr1.fsf@gmail.com>

Al Haji-Ali <abdo.haji.ali@gmail.com> writes:

> The variable `mm-inline-override-types` is overridden in `notmuch-show` to "stop application/* parts from being displayed".
>
> This works well, however it means in other places the part *is* expanded. For example when `(notmuch-show-refresh-view)` is called (after any refresh) or even when `notmuch-show-reply-sender` is called.
>
> To see this behaviour make sure that `mm-inline-override-types` is nil and open a message with an `application/zip` part. The part is not expanded as expected.
> Call `(notmuch-show-refresh-view)` and notice how the part is expanded (on my Emacs, I even get a warning: "These default coding systems were tried to encode the following problematic characters in the buffer ‘ *temp*-926949’").
>
> I solved this in my config by setting `mm-inline-override-types` to `(list "application/*")`, but I think notmuch could be more consistent.
>

Thanks for the report. I can duplicate the issue with
notmuch-show-refresh-view. I believe with notmuch-show-reply-sender is
fixed in git master (90a7c1af368a527700dcde9b0dcbd760afc7bd92).

d\r

  reply	other threads:[~2022-07-27 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 17:08 Overriding mm-inline-override-types in notmuch-show Al Haji-Ali
2022-07-27 16:26 ` David Bremner [this message]
2022-08-11 10:53   ` David Bremner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bktaa5dn.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=abdo.haji.ali@gmail.com \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).