Matthew Lear writes:
> I'm of the opinion that this is probably some sort of set up /
> configuration issue specific to 25, but I'm quite surprised. I don't
> have many settings for handling html stuff:
>
> (setq mm-text-html-renderer 'shr)
> (setq shr-inhibit-images nil)
> (setq mime-view-text/h
Hi David. Finally got back round to checking this with recent sw. Apologies
for the long delay. I can confirm that the problem still exists as before,
ie replying to my test html emails when composing the message in a new
frame throws the bodypart errors. ...But I'm not too fussed about it
because
Matthew Lear writes:
> It was indeed fixed...that is until I updated my emacs git tree to 25.2.1.
> I've given up composing emails in new frames as it's now broken again -
> this time when replying to emails which have quoted/embedded html in the
> body. Feels like two steps forward, one step ba
On 4 Mar 2017 11:03, "David Bremner" wrote:
David Bremner writes:
> Matthew Lear writes:
>
>
>> Thanks David. Yes it does. After recompiling the v25 lisp with these
>> changes, I'm unable to reproduce the problems with both the test emails I
>> sent you. Wonderful :-)
>> Are you going to raise
David Bremner writes:
> Matthew Lear writes:
>
>
>> Thanks David. Yes it does. After recompiling the v25 lisp with these
>> changes, I'm unable to reproduce the problems with both the test emails I
>> sent you. Wonderful :-)
>> Are you going to raise this with upstream?
>> Cheers,
>> Matt
>
> Y
Matthew Lear writes:
> Thanks David. Yes it does. After recompiling the v25 lisp with these
> changes, I'm unable to reproduce the problems with both the test emails I
> sent you. Wonderful :-)
> Are you going to raise this with upstream?
> Cheers,
> Matt
Yes, I've filed
https://debbugs.
On 18 Feb 2017 01:01, "David Bremner" wrote:
So I _finally_ got around to looking at these, and I think it's roughly
the same shr bug as before but some different functions.
I could actually only duplicate the bug with emacs-reply-fail-ec
message, but that was fixed by the following patch again
Matthew Lear writes:
> On 03/12/16 01:58, David Bremner wrote:
>> Matthew Lear writes:
>>
>>>
>>> I'd happily post some debug info to help analyse this if somebody could
>>> give me a few pointers about what would be needed and the emacs-fu
>>> needed to generate this.
>>>
>>
>> I think the be
On 03/12/16 01:58, David Bremner wrote:
> Matthew Lear writes:
>
>>
>> I'd happily post some debug info to help analyse this if somebody could
>> give me a few pointers about what would be needed and the emacs-fu
>> needed to generate this.
>>
>
> I think the best thing at this point would be to
Matthew Lear writes:
>
> I'd happily post some debug info to help analyse this if somebody could
> give me a few pointers about what would be needed and the emacs-fu
> needed to generate this.
>
I think the best thing at this point would be to find (or create)
another public message where you ca
On 23/11/16 11:57, David Bremner wrote:
> In a fresh emacs, can you generate an error using the recipe in
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24950 ?
No. I can evaluate the recipe ok and eval of the last line yields:
10 (#o12, #xa, ?\C-j)
__
Matthew Lear writes:
> I'd happily post some debug info to help analyse this if somebody could
> give me a few pointers about what would be needed and the emacs-fu
> needed to generate this.
>
> Cheers,
> -- Matt
In a fresh emacs, can you generate an error using the recipe in
https://deb
On 22/11/16 14:24, Matthew Lear wrote:
> I can confirm that it is indeed fixed. I'm not able to reproduce it with
> the latest emacs 25 from git.
Unfortunately, it seems I was too hasty in confirming this.
For some reason unknown to me, replying to the html in some
multipart/alternative works fine
On 20/11/16 20:01, David Bremner wrote:
>> I have reported https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24950
>> upstream. We'll see if they agree it's bug in shr.
>
> This bug will be fixed in the next release of emacs 25, so I'm tagging
> it fixed.
I can confirm that it is indeed fixed. I'm no
David Bremner writes:
> David Bremner writes:
>
>> Yes, I can replicate this bug in emacs 25.1 by
>>
>> 1) ./devel/try-emacs-mua -q
>>
>> 2) (setq notmuch-mua-compose-in 'new-frame)
>>
>> 3) reply to an html only message.
>>
>> If I M-x toggle-debug-on-error I get a backtrace ending in
>>
>> set
David Bremner writes:
> Yes, I can replicate this bug in emacs 25.1 by
>
> 1) ./devel/try-emacs-mua -q
>
> 2) (setq notmuch-mua-compose-in 'new-frame)
>
> 3) reply to an html only message.
>
> If I M-x toggle-debug-on-error I get a backtrace ending in
>
> set-window-buffer(nil #)
> shr-pixel-colu
Matthew Lear writes:
> (setq notmuch-mua-compose-in 'new-frame)
> (setq notmuch-multipart/alternative-discouraged '("text/plain"))
Using devel/try-emacs-mua in the source tree, only these last two lines
are needed. But yes agree, after discouraging text/plain, multipart
messages can also duplic
On 12/11/16 00:20, David Bremner wrote:
> Matthew Lear 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
> mult
Matthew Lear writes:
> I can trigger the bug if I discard text/plain though. Did you try that?
> Original message From: David Bremner
> Date: 11/11/2016 11:40 (GMT+00:00) To: Matthew Lear ,
> Matt Armstrong Cc: notmuch@notmuchmail.org Subject:
> Re: s
I can trigger the bug if I discard text/plain though. Did you try that?
Original message From: David Bremner Date:
11/11/2016 11:40 (GMT+00:00) To: Matthew Lear , Matt
Armstrong Cc: notmuch@notmuchmail.org Subject: Re: some
issues with emacs 25
Matthew Lear writes:
>
Matthew Lear writes:
> On 09/11/16 23:55, David Bremner wrote:
>> I can't find an html only public-message so far to give a full
>> backtrace.
> If it helps, here is some text in *bold *with some changes in red that
> you can test with :-D
FWIW, this doesn't trigger the bug with default settings
On 09/11/16 23:55, David Bremner wrote:
> Matthew Lear writes:
>
>> On 28/10/16 22:34, Matthew Lear wrote:
>>> I will commence with trying to figure out what is causing the problem. I've
>>> seen some weirdness with margins when viewing HTML messages too. Maybe
>>> that's some kind of bizarre to
Matthew Lear writes:
> On 28/10/16 22:34, Matthew Lear wrote:
>>
>> I will commence with trying to figure out what is causing the problem. I've
>> seen some weirdness with margins when viewing HTML messages too. Maybe
>> that's some kind of bizarre toolkit thing... Anyway, thanks a lot for
>>
On 28/10/16 22:34, Matthew Lear wrote:
>
> I will commence with trying to figure out what is causing the problem. I've
> seen some weirdness with margins when viewing HTML messages too. Maybe that's
> some kind of bizarre toolkit thing... Anyway, thanks a lot for testing and
> for confirming th
> On 28 Oct 2016, at 01:52, Matt Armstrong wrote:
>
> Matthew Lear writes:
>
>> Hi,
>> I switched to trying emacs 25 (25.1) with notmuch the other day.
>
> I'm on 25.1 as well, but haven't experienced the symptoms you describe.
Thanks Matt. I feel reassured! :-) I will commence with trying t
Matthew Lear writes:
> Hi,
> I switched to trying emacs 25 (25.1) with notmuch the other day.
I'm on 25.1 as well, but haven't experienced the symptoms you describe.
>> !!! Bodypart handler `notmuch-show-insert-part-text/html' threw an error:
>> !!! Window is dedicated to ‘*unsent mail to u...@
Hi,
I switched to trying emacs 25 (25.1) with notmuch the other day. I
really like some of the improvements that have been made (in particular,
SHR seems to do a much nicer and quicker job of rendering html emails).
However, things came a little unstuck when I tried to reply to an email
with notmuc
27 matches
Mail list logo
