From: Chong Yidong <cyd@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Katsumi Yamaoka <yamaoka@jpl.org>,
Paul Eggert <eggert@cs.ucla.edu>,
Stefan Monnier <monnier@IRO.UMontreal.CA>,
emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r107264: shr.el (shr-rescale-image): Allow viewing large images.
Date: Wed, 15 Feb 2012 14:42:16 +0800 [thread overview]
Message-ID: <87y5s4tx6f.fsf@gnu.org> (raw)
In-Reply-To: <87aa4le0g0.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 14 Feb 2012 19:26:07 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> As Stefan says, perhaps this limit should be reworked to be, er,
> different (based on total pixels or total size), but we're too late in
> the release cycle for that, aren't we?
The variable already accepts integer values to specify maximum pixel
width/height. If memory serves, the reason we put it as a multiple of
the frame height/width has to do with the idea that it's generally
useless to show an image much larger than the typical frame size (even
with scrolling). The distinction doesn't seem hugely important in
practice.
next prev parent reply other threads:[~2012-02-15 6:42 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
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 [this message]
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=87y5s4tx6f.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=yamaoka@jpl.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.