From: Andreas Schwab <schwab@linux-m68k.org>
To: "Adam Sjøgren" <asjo@koldfront.dk>
Cc: ding@gnus.org
Subject: Re: images in article view
Date: Sat, 07 Sep 2019 12:14:54 +0200 [thread overview]
Message-ID: <87ftl8l8f5.fsf@igel.home> (raw)
In-Reply-To: <87a7bgcxs3.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Sat, 07 Sep 2019 10:31:56 +0200")
On Sep 07 2019, Adam Sjøgren <asjo@koldfront.dk> wrote:
> Eric writes:
>
>> it seems that mm-inline-large-images-proportion has some effect on
>> images in mime messages, with mm-inline-large-images set to 'resize.
>
> Is it just me, or is the documentation of the latter kind of convoluted?
>
> ,----[ C-h v mm-inline-large-images RET ]
> | mm-inline-large-images is a variable defined in ‘mm-decode.el’.
> | Its value is nil
> |
> | Documentation:
> | If t, then all images fit in the buffer.
> | If ‘resize’, try to resize the images so they fit.
> |
> | You can customize this variable.
> `----
>
> How does it make "images fit in the buffer" (t), without resizing them,
> which has it's own option (resize)?!
When t, images are not resized, and will stick out of the window when
too large. Otherwise, images are either resized to fit, or not inlined
at all.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-09-07 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 16:14 Eric S Fraga
2019-09-07 8:25 ` Eric S Fraga
2019-09-07 8:31 ` Adam Sjøgren
2019-09-07 9:01 ` Eric S Fraga
2019-09-07 10:14 ` Andreas Schwab [this message]
2019-09-07 15:30 ` Eric S Fraga
2019-09-16 20:23 ` Lars Ingebrigtsen
2019-09-20 16:23 ` Eric S Fraga
2019-09-16 20:31 ` 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=87ftl8l8f5.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=asjo@koldfront.dk \
--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).