Re: display word wrapping

[Kim F. Storm]

Juanma Barranquero <address@hidden> writes:

> On Thu, 03 Jun 2004 08:49:46 +0100
> Jason Rumney <address@hidden> wrote:

> > It seems we will have to do it from startup.el, after loading the
> > init files.
>
> Perhaps it would make sense to add it to after-init-hook in
> term/*-win.el modules.

You could modify image-type-available-p to do it on the fly:

(defun image-type-available-p (type)
  "Value is non-nil if image type TYPE is available.
Image types are symbols like `xbm' or `jpeg'."
  (when (and (boundp 'image-library-alist) image-library-alist)
     (init-image-libraries image-library-alist)
     (setq image-library-alist nil))
  (and (boundp 'image-types) (not (null (memq type image-types)))))

This would have the effect that the user could try different settings
of image-library-alist and just use the normal image functions to
have the changes loaded on the fly.

>
> > Make sure that running it a second time has no bad effects. Ideally,
> > it should try to load only those image libraries that are not already
> > supported.
>

The above patch guards against that to some extent, but explicitly skipping
those elements which are already in image-types is a good thing.


As you see, I also changed the variable to image-library-alist -- there's
no need to emphasize that this is w32 specific (other systems may need it
later).

Finally, I propose to specify the alist as arg to init-image-libraries;
there's no need to "pollute" the C code with a Vw32_image_libraries_alist
variable.

--
Kim F. Storm <address@hidden> http://www.cua.dk