Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: What factors affect the placement of inline images?
Date: 24 May 2001 21:48:32 -0400	[thread overview]
Message-ID: <ygen18219n3.fsf@asfast.com> (raw)

Is anyone willing to explain all the factors that could affect the
placement of inline images in messages displayed in Gnus?

What I'm looking for is a list of the variables that determine image
placement, as well as the standard Gnus behavior w/r/t mime types and
message parts that have an effect on the placement of inline images.
I'm talking about images that are small enough to be displayed within
the message window.

As you know, I recently posted a query about a problem I started
noticing in Gnus after I upgraded from XEmacs 21.2.44 to XEmacs
21.4.3.  In the earlier version of XEmacs, multipart messages whose
topmost part contained the encoding of an image would cause the image
displayed to be displayed at the top of the message buffer, with text
(or whatever) in subsequent message parts being shown below the inline
image.

However, after the XEmacs 21.4.3 upgrade (and with the same version of
Gnus), these same multipart messages show the inline image from the
topmost message part at the bottom of the message buffer, irrspective
of the disposition ("attachment", "inline", or no disposition).

Clearly, this change in image positioning has to do with my use of the
newer version of XEmacs, but I suspect that the problem is occurring
because of Gnus' use of one or more xemacs functions whose behavior
might have changed in very recent versions of XEmacs.

This is the reason for my query.  If someone could explain the factors
which could affect Gnus' decision as to where to place inline images,
I will then dig through the elisp in my Gnus and XEmacs installation
to try to figure out why this is happening ... and then, to make my
findings known to this group.

By the way, I'm now using the early-morning-of-May-24 CVS version of
Gnus.

Thanks in advance.

-- 
 Lloyd Zusman
 ljz@asfast.com


                 reply	other threads:[~2001-05-25  1:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=ygen18219n3.fsf@asfast.com \
    --to=ljz@asfast.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).