From: Mark Walters <markwalters1009@gmail.com>
To: David Bremner <david@tethera.net>,
Tomas Nordin <tomasn@posteo.net>,
notmuch@notmuchmail.org
Subject: Re: [PATCH v2] emacs: show: stop display of application/* parts
Date: Mon, 27 Feb 2017 08:31:15 +0000 [thread overview]
Message-ID: <8737f0qbl8.fsf@qmul.ac.uk> (raw)
In-Reply-To: <87efz2ma7r.fsf@rocinante.cs.unb.ca>
Hi
>> But what will we do if the user has not customized it because she
>> /wants/ to display all possible things inline. I have not seen that this
>> patch is merged into master, and probably, when I have learned about
>> this variable, I think maybe it's better not to do it in the notmuch
>> code.
Well they can set mm-inline-override-types to
"non-existent/type". Rather a kludge I agree.
> The problem is that the gnus default is somehow unsafe, and causes bad
> behaviour for people receiving large attachments.
I agree with this and do think we should block this by default. In
particular, gnus/mm stuff doesn't even check for the existence of unzip
before running it on zip attachments so on my machines which don't have
unzip I get a bodypart insertion error.
One alternative would be to add a variable
notmuch-mm-inline-override-types which would combine or replace
mm-inline-override-types for notmuch's use. A defcustom would be
clutter, but a variable would mean anyone with unusual requirements
could just setq it.
What does anyone think?
Best wishes
Mark
next prev parent reply other threads:[~2017-02-27 8:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 21:25 [PATCH] emacs: show: stop display of appliaction/* parts Mark Walters
2017-01-07 23:12 ` Tomas Nordin
2017-01-08 12:22 ` David Bremner
2017-01-08 13:09 ` Tomi Ollila
2017-01-08 17:44 ` Tomi Ollila
2017-01-08 19:52 ` Tomas Nordin
2017-01-08 21:49 ` Tomi Ollila
2017-01-28 9:47 ` [PATCH v2] emacs: show: stop display of application/* parts Mark Walters
2017-02-12 22:53 ` Tomas Nordin
2017-02-13 14:33 ` David Bremner
2017-02-27 8:31 ` Mark Walters [this message]
2017-02-27 9:00 ` Tomi Ollila
2017-02-27 20:36 ` Tomas Nordin
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=8737f0qbl8.fsf@qmul.ac.uk \
--to=markwalters1009@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=tomasn@posteo.net \
/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).