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

> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 21 Jun 2013 09:40:26 +0200
> 
> 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?

> And I think that's the common use case, actually.  When displaying
> images in Emacs, we seldom want to display images that are bigger than
> the frame, because Emacs doesn't really deal with that situation
> ideally.

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.

So my recommendation would be not to base development on this
assumption.

The user might legitimately want not to download large images, but for
that, we already have max-image-size and check_image_size, no?



  reply	other threads:[~2013-06-21  9:55 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 ` Eli Zaretskii [this message]
2013-06-21 10:08   ` :max-width/:max-height Lars Magne Ingebrigtsen
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=837ghnokij.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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).