From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 36773-done@debbugs.gnu.org, larsi@gnus.org, plaiceadam@gmail.com
Subject: bug#36773: 27.0.50; Accessing a cached SVG with eww can cause Emacs to crash
Date: Sat, 27 Jul 2019 13:58:46 +0300 [thread overview]
Message-ID: <83zhkzlp5l.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBfBsVoLZo_jJJsgzT7HrQaKcDc3enP=6Q9bwR--a40r6A@mail.gmail.com> (message from Pip Cet on Thu, 25 Jul 2019 14:14:43 +0000)
> From: Pip Cet <pipcet@gmail.com>
> Date: Thu, 25 Jul 2019 14:14:43 +0000
> Cc: larsi@gnus.org, plaiceadam@gmail.com, 36773@debbugs.gnu.org
>
> > > I misread what you wrote at first, but I like my misreading better:
> > > url-handle-content-transfer-encoding modifies the message, but not its
> > > headers. Why shouldn't it do both?
> >
> > Yes, I think it should. Because that's the root cause of the problem:
> > the data is uncompressed, but the headers still say it is compressed.
>
> Okay, I think it's likely we're going to require something similar for
> other headers, so I added an argument to mail-fetch-field to delete
> the fetched field's header line(s).
>
> Patches attached (the first should be unmodified). Appears to work here.
Thanks, I've now pushed your second patch, and I'm closing this bug.
next prev parent reply other threads:[~2019-07-27 10:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 16:40 bug#36773: 27.0.50; Accessing a cached SVG with eww can cause Emacs to crash adam plaice
2019-07-23 18:37 ` Pip Cet
2019-07-23 19:33 ` Adam Plaice
2019-07-23 20:06 ` Pip Cet
2019-07-23 21:13 ` Adam Plaice
2019-07-24 13:24 ` Pip Cet
2019-07-24 14:46 ` Eli Zaretskii
2019-07-24 18:28 ` Pip Cet
2019-07-24 19:11 ` Eli Zaretskii
2019-07-24 22:13 ` Adam Plaice
2019-07-25 12:05 ` Pip Cet
2019-07-25 9:38 ` Lars Ingebrigtsen
2019-07-25 11:51 ` Pip Cet
2019-07-25 12:55 ` Eli Zaretskii
2019-07-25 14:14 ` Pip Cet
2019-07-25 22:14 ` Adam Plaice
2019-07-27 10:58 ` Eli Zaretskii [this message]
2019-07-25 17:09 ` Lars Ingebrigtsen
2019-07-25 21:37 ` Paul Eggert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83zhkzlp5l.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36773-done@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=pipcet@gmail.com \
--cc=plaiceadam@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.