unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <jmbarranquero@wke.es>
Cc: Andreas Schwab <schwab@suse.de>,
	emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: [PATCH] Delayed loading of image libraries
Date: Fri, 02 Jul 2004 10:34:00 +0200	[thread overview]
Message-ID: <20040702102722.CF3A.JMBARRANQUERO@wke.es> (raw)
In-Reply-To: <x57jtmu8tz.fsf@lola.goethe.zz>


On 02 Jul 2004 10:11:52 +0200
David Kastrup <dak@gnu.org> wrote:

> The way I understand this, the responsibility of making the library
> available rests on the display code.

Yes.

> If it is, I have failed to get it.  It sounded to me like you were
> proposing that the user has to something before the image cn be
> displayed.

No!  What I say is that the display code should call
image-type-available-p before trying to lookup image type or determine
whether the image type is valid.

> What if a program does not care because it simply assumes that the
> configuration is correct?  If a particular format is not supported,
> we currently just get boxes.  That's ok.  It is not ok if we just get
> boxes even _when_ a particular format is supported.

That certainly does not happen if you open an image file and are using
auto-image-file-mode, for example.  From this discussion, I gather that
it does happen if you use create-image, save the result and then load it
and try to display it...

                                                                Juanma

  reply	other threads:[~2004-07-02  8:34 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10 12:38 [PATCH] Delayed loading of image libraries Juanma Barranquero
2004-06-30 10:15 ` Andreas Schwab
2004-06-30 11:13   ` Juanma Barranquero
2004-06-30 11:24     ` Andreas Schwab
2004-06-30 11:34       ` Juanma Barranquero
2004-06-30 11:41         ` Andreas Schwab
2004-06-30 13:00           ` Juanma Barranquero
2004-06-30 15:42         ` Miles Bader
2004-07-01  9:30           ` Juanma Barranquero
2004-07-01  9:48             ` Miles Bader
2004-07-01 10:13               ` Juanma Barranquero
2004-07-02  1:16                 ` Miles Bader
2004-07-02  7:02                   ` Juanma Barranquero
2004-07-02  7:10                     ` David Kastrup
2004-07-02  7:41                       ` Juanma Barranquero
2004-07-02  7:56                         ` Miles Bader
2004-07-02  8:10                           ` Juanma Barranquero
2004-07-02  8:20                             ` Miles Bader
2004-07-02  8:45                               ` Juanma Barranquero
2004-07-02  8:59                                 ` Miles Bader
2004-07-02  9:02                                   ` Miles Bader
2004-07-02  8:11                         ` David Kastrup
2004-07-02  8:34                           ` Juanma Barranquero [this message]
2004-07-03 18:21                     ` Richard Stallman
2004-06-30 14:19       ` Stefan

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040702102722.CF3A.JMBARRANQUERO@wke.es \
    --to=jmbarranquero@wke.es \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.org \
    --cc=schwab@suse.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).