From: Karl Kleinpaste <karl@justresearch.com>
Subject: image/jpeg is viewed externally?!?
Date: 24 Nov 1998 14:33:58 -0500 [thread overview]
Message-ID: <vxkn25ganrt.fsf@beaver.jprc.com> (raw)
Is there some sort of image size boundary, beyond which p0.54 decides
to invoke xv(1) for viewing, rather than doing so inline in XEmacs?
I've been sending myself a bunch of test messages, using `C-c C-a'
just to try it out. If I send myself a copy of the miniature rms.jpg
image Lars has been using in the MIME tests, that displays fine. If I
send myself a random image that fits comfortably within the display
limits of my *Article* buffer, that too displays fine.
But if I send myself a 517x768 image/jpeg, Gnus spawns xv(1) for it.
I'm not hallucinating, honest -- from my *Message-Log* buffer:
Generating summary...done
Viewing with xv %s
Displaying xv /tmp/emm.a20268/mm.a20268...
I expected the image to be displayed directly, as other images had
been. What are the conditions under which xv is preferred over direct
display by XEmacs?
next reply other threads:[~1998-11-24 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-24 19:33 Karl Kleinpaste [this message]
1998-11-24 20:20 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vxkn25ganrt.fsf@beaver.jprc.com \
--to=karl@justresearch.com \
/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).