unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: :max-width/:max-height
Date: Fri, 21 Jun 2013 12:08:40 +0200	[thread overview]
Message-ID: <m3mwqju66v.fsf@stories.gnus.org> (raw)
In-Reply-To: <837ghnokij.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 21 Jun 2013 12:55:48 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> It was probably lost in that long bickering thread about whether
>> lookup_image pushed stuff over X or not, but I realised that the
>> interface shr needs is :max-width and :max-height on images.
>
> What would such an interface provide to its callers?

I'm not sure I understand the question.  It would allow scaling the
images to fit in a window without having to do the tedious computations
in the caller, and it would require decoding the image only once.

> I wouldn't recommend assuming that Emacs doesn't deal well with large
> images.  Changes committed lately already make it deal much better
> with vertical scrolling, and doing the same for horizontal scrolling
> should be easy.

You've made it much better lately, but it's still awkward.  However,
that's not the main point.  When you ask Emacs to display an image, you
usually don't want to see a section of the image -- you want to see the
entire thing.  This is what Firefox does, for instance, if you ask it to
display a single image that is too large for its window.

shr has functions for zooming in the scaled image afterwards, if you
really want to see the details, of course.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  reply	other threads:[~2013-06-21 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21  7:40 :max-width/:max-height Lars Magne Ingebrigtsen
2013-06-21  9:55 ` :max-width/:max-height Eli Zaretskii
2013-06-21 10:08   ` Lars Magne Ingebrigtsen [this message]
2013-06-21 10:21     ` :max-width/:max-height Eli Zaretskii
2013-06-21 10:29       ` :max-width/:max-height Lars Magne Ingebrigtsen
2013-06-21 10:47         ` :max-width/:max-height Eli Zaretskii
2013-06-23 19:26           ` :max-width/:max-height Lars Magne Ingebrigtsen

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3mwqju66v.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=eliz@gnu.org \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).