From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Standardize image height for the article's in-line display
Date: Wed, 01 Feb 2012 21:47:57 +0100 [thread overview]
Message-ID: <8762fq701u.fsf@gnus.org> (raw)
In-Reply-To: <87mx92wcov.fsf@lifelogs.com> (Ted Zlatanov's message of "Wed, 01 Feb 2012 14:55:44 -0500")
Ted Zlatanov <tzz@lifelogs.com> writes:
> That works for me, if it's easy to implement.
Apparently it was. Give it a whirl.
It needs a bit of tweaking, though. When making the image sliced, the
underlines from the <a href> thing are pasted all throughout the image.
Yuck.
That is, if you have a <a href><img> image...
I'm not sure what the most "elegant" solution here would be. It'll be a
kludge anyway...
And there's a bit of ad-hoc-ery going on with "what is one image" now,
since sliced images are really lots of smaller images. That has to be
cleaned up, but as a proof of concept, it probably... proves the
concept.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Sent from my Rome
next prev parent reply other threads:[~2012-02-01 20:47 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
2012-02-01 20:47 ` Lars Ingebrigtsen [this message]
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=8762fq701u.fsf@gnus.org \
--to=larsi@gnus.org \
--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).