From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Standardize image height for the article's in-line display
Date: Wed, 01 Feb 2012 14:55:44 -0500 [thread overview]
Message-ID: <87mx92wcov.fsf@lifelogs.com> (raw)
In-Reply-To: <87fweu72nd.fsf@gnus.org>
On Wed, 01 Feb 2012 20:51:50 +0100 Lars Ingebrigtsen <larsi@gnus.org> wrote:
LI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> I'd also like some more control over SHR's image scaling. When point is
>> on an image, `z' or some such keybinding should iterate between native
>> size, zoomed to max(buffer width, buffer height), and zoomed to frame
>> size.
LI> Yes, that sounds like a good idea. Frequently when I'm looking at the
LI> 9gag feed, there are pictures that are too small to read, which means
LI> that I have to hit the link and read the message in (EWWWW!!!1!ONE!!)
LI> Firefox.
LI> But what about the images that are too big for the Emacs frame? As we
LI> know, it's virtually impossible to scroll these images in Emacs...
LI> Oh! I know! The `z' command could insert big images as "striped"
LI> images, allowing scrolling? Striped images are really slow, which is
LI> why they're not used by default, but for an interactive command, it
LI> would make total sense.
LI> What do you think?
That works for me, if it's easy to implement.
Ted
next prev parent reply other threads:[~2012-02-01 19:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 18:10 Vitalie Spinu
2012-02-01 18:02 ` Ted Zlatanov
2012-02-01 19:51 ` Lars Ingebrigtsen
2012-02-01 19:55 ` Ted Zlatanov [this message]
2012-02-01 20:47 ` Lars Ingebrigtsen
2012-02-01 21:49 ` Ted Zlatanov
2012-02-01 23:15 ` Lars Ingebrigtsen
2012-02-01 23:20 ` Ted Zlatanov
2012-02-01 23:23 ` Lars Ingebrigtsen
2012-02-01 23:38 ` Ted Zlatanov
2012-02-02 7:11 ` Reiner Steib
2012-02-02 9:34 ` Lars Ingebrigtsen
2012-02-02 11:15 ` Vitalie Spinu
2012-02-02 12:01 ` Lars Ingebrigtsen
2012-02-02 9:54 ` Lars Ingebrigtsen
2012-02-02 10:01 ` Lars Ingebrigtsen
2012-02-02 8:20 ` Antoine Levitt
2012-02-02 9:51 ` Lars Ingebrigtsen
2012-02-01 19:48 ` Lars Ingebrigtsen
2012-02-01 20:10 ` Vitalie Spinu
2012-02-01 23:17 ` Lars 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mx92wcov.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@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.
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 NNTP newsgroup(s).