From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r107264: shr.el (shr-rescale-image): Allow viewing large images.
Date: Mon, 13 Feb 2012 15:41:51 -0500 [thread overview]
Message-ID: <874nuu1n5c.fsf@lifelogs.com> (raw)
In-Reply-To: 8762fawk1t.fsf@gnus.org
On Mon, 13 Feb 2012 21:33:02 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Paul Eggert <eggert@cs.ucla.edu> writes:
>> For incredibly large images, the underlying libraries are
>> likely to have unchecked integer or memory overflows, dumping
>> core if you're lucky and having "interesting" behavior otherwise.
>> Even if the libraries themselves are reliable (a big "if"),
>> that part of Emacs is less well ironed out, and I wouldn't
>> be surprised if Emacs proper has exploitable bugs in this
>> area.
LI> Right. But the default value of 6.0 disallows a lot of real-world
LI> images. (9gag in particular.) Perhaps binding it to, say, 60.0 in
LI> shr.el would make sense?
Or make `max-image-size' a plist of conditions, so filtering by absolute
size AND by relative size to frame AND by file size are all possible at
once?
Ted
next prev parent reply other threads:[~2012-02-13 20:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1RwnLm-0007NV-Lm@vcs.savannah.gnu.org>
2012-02-13 13:15 ` [Emacs-diffs] /srv/bzr/emacs/trunk r107264: shr.el (shr-rescale-image): Allow viewing large images Stefan Monnier
2012-02-13 19:57 ` Andy Moreton
2012-02-13 20:03 ` Lars Ingebrigtsen
2012-02-13 20:01 ` [Emacs-diffs] " Lars Ingebrigtsen
2012-02-13 20:29 ` Paul Eggert
2012-02-13 20:33 ` Lars Ingebrigtsen
2012-02-13 20:41 ` Ted Zlatanov [this message]
2012-02-15 6:26 ` Chong Yidong
2012-02-15 13:40 ` Ted Zlatanov
2012-02-14 8:20 ` Paul Eggert
2012-02-14 14:49 ` Lars Ingebrigtsen
2012-02-14 15:56 ` Paul Eggert
2012-02-14 18:26 ` Lars Ingebrigtsen
2012-02-15 6:42 ` Chong Yidong
2012-02-15 6:27 ` Chong Yidong
2012-02-14 17:43 ` Stefan Monnier
2012-02-13 21:24 ` Stefan Monnier
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=874nuu1n5c.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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 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.