unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Matthew Lear <matt@bubblegen.co.uk>
To: David Bremner <david@tethera.net>,
	Matt Armstrong <marmstrong@google.com>
Cc: notmuch@notmuchmail.org
Subject: Re: some issues with emacs 25
Date: Mon, 14 Nov 2016 11:17:06 +0000	[thread overview]
Message-ID: <58299D32.5080003@bubblegen.co.uk> (raw)
In-Reply-To: <87eg2ha6rv.fsf@tethera.net>

On 12/11/16 00:20, David Bremner wrote:
> Matthew Lear <matt@bubblegen.co.uk> writes:
> 
>> I can trigger the bug if I discard text/plain though. Did you try that? 
> 
> I'm not sure what you mean by "discard", but closing it isn't enough. I
> think more of your settings are needed to replicate the problem with a
> multipart/alternative message.
> 

Apologies, David. I wasn't clear at all. I meant that if I discourage
text/plain in a multipart/alternative message, I can trigger the bug.
If I use the following tiny-init.el...

(require 'shr)
(setq mm-text-html-renderer 'shr)
(setq mime-view-text/html-previewer 'shr)
(setq mm-html-inhibit-images nil)
(setq mm-html-blocked-images nil)

(require 'notmuch)
(global-set-key [f1]  'notmuch)
(setq notmuch-mua-compose-in 'new-frame)
(setq notmuch-multipart/alternative-discouraged '("text/plain"))


...and load it using 'emacs-25 -q --load ~/.emacs.d/tiny-init.el',
searching for any mimetype:text/html and replying to it triggers the bug
for me.

Commenting out the setting of notmuch-mua-compose-in is enough to
prevent the problem from occurring.
Cheers,
--  Matt

  reply	other threads:[~2016-11-14 11:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-11 13:25 some issues with emacs 25 Matthew Lear
2016-11-12  0:20 ` David Bremner
2016-11-14 11:17   ` Matthew Lear [this message]
2016-11-16  2:16     ` David Bremner
  -- strict thread matches above, loose matches on Subject: below --
2016-10-27 20:56 Matthew Lear
2016-10-28  0:52 ` Matt Armstrong
2016-10-28 21:34   ` Matthew Lear
2016-11-09 18:02     ` Matthew Lear
2016-11-09 23:55       ` David Bremner
2016-11-10 14:49         ` Matthew Lear
2016-11-11 11:40           ` David Bremner
2016-11-16  2:50         ` David Bremner
2016-11-20 20:01           ` David Bremner
2016-11-22 14:24             ` Matthew Lear
2016-11-23  9:44               ` Matthew Lear
2016-11-23 11:57                 ` David Bremner
2016-11-23 16:18                   ` Matthew Lear
2016-12-03  1:58                 ` David Bremner
2017-01-04 16:31                   ` Matthew Lear
2017-02-18  1:01                     ` David Bremner
2017-02-21 10:49                       ` Matthew Lear
2017-02-21 11:40                         ` David Bremner
2017-03-04 11:03                           ` David Bremner
2017-04-28 16:03                             ` Matthew Lear
2017-06-30 12:47                               ` David Bremner
2017-10-19 11:11                                 ` Matthew Lear
2017-11-12 15:16 ` 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=58299D32.5080003@bubblegen.co.uk \
    --to=matt@bubblegen.co.uk \
    --cc=david@tethera.net \
    --cc=marmstrong@google.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).