Re: About `image-load-path'

Re: About `image-load-path'

[David PONCE]

Hello,

>     Yes it makes sense to let-bind `image-load-path' in my own code
>     but it is not so easy for libraries which are part of Emacs for
>     example.
> 
> Could you give an example of where you would want to do this
> in the code of a library that is part of Emacs?

I don't want to change the code of existing libraries.  Just to easily
use different sets of images.

For example, I use a different set of toolbar icons. I just put the
new ones (with same names) in a directory in my `load-path' (I have to
add 'tool-bar-setup' to `after-init-hook' too to refresh the pre-built
`tool-bar-map'), and voilà!

With the current setting of `image-load-path', if the default toolbar
icons are put in etc/images those in my `load-path' will be
ignored. To take them into account again, I'll have to change the
default value of `image-load-path' in my init file to search the
`load-path' first, or to add it my own image directory.  That's why I
suggested to at least make `image-load-path' customizable.

Anyway no problem for me ;-)

Sincerely,
David

Re: About `image-load-path'

[Richard M. Stallman]

    For example, I use a different set of toolbar icons. I just put the
    new ones (with same names) in a directory in my `load-path' (I have to
    add 'tool-bar-setup' to `after-init-hook' too to refresh the pre-built
    `tool-bar-map'), and voilà!

With the new code, you wou have to modify image-load-path too.
I don't think that is so difficult.

    To take them into account again, I'll have to change the
    default value of `image-load-path' in my init file to search the
    `load-path' first, or to add it my own image directory.  That's why I
    suggested to at least make `image-load-path' customizable.

It does not need to be officially customizable
for you to set it in your init file.
(There are problems using Custom to set variables like this one.)

Re: About `image-load-path'

[David Kastrup]

"Richard M. Stallman" <rms@gnu.org> writes:

>     For example, I use a different set of toolbar icons. I just put the
>     new ones (with same names) in a directory in my `load-path' (I have to
>     add 'tool-bar-setup' to `after-init-hook' too to refresh the pre-built
>     `tool-bar-map'), and voilà!
>
> With the new code, you wou have to modify image-load-path too.
> I don't think that is so difficult.

Maybe image-load-path could also allow symbols.  Then one could make
its last element the symbol `load-path', and thus it would be able to
track changes of load-path.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: About `image-load-path'

[Reiner Steib]

On Sat, Sep 24 2005, David Kastrup wrote:

> Maybe image-load-path could also allow symbols.  Then one could make
> its last element the symbol `load-path', and thus it would be able to
> track changes of load-path.

`image-load-path' already allows symbols (rev. 1.50 of `image.el').  I
think making it customizable would make sense if paths like
(file-name-as-directory (expand-file-name "images" data-directory) do
not end up in the custom file in *expanded* form.

Instead of...

'(image-load-path
  (quote ("/some/user/image/dir"
          "/some/path/to/emacs/prefix/share/emacs/22.0.50/etc/images/"
	  data-directory
	  load-path)))

...  it should read...

'(image-load-path
  (quote ("/some/user/image/dir"
          (file-name-as-directory (expand-file-name "images" data-directory))
	  data-directory
	  load-path)))

... in the custom file.

Here's an attempt (maybe my tests are not the most suitable ones?) to
achieve this:

--8<---------------cut here---------------start------------->8---
--- image.el	19 Sep 2005 11:36:26 +0200	1.50
+++ image.el	22 Sep 2005 14:52:09 +0200	
@@ -49,15 +49,18 @@
 with one argument, a string containing the image data.  If PREDICATE returns
 a non-nil value, TYPE is the image's type.")

-(defvar image-load-path
-  (list (file-name-as-directory (expand-file-name "images" data-directory))
+(defcustom image-load-path
+  (list '(file-name-as-directory (expand-file-name "images" data-directory))
 	'data-directory 'load-path)
   "List of locations in which to search for image files.
 If an element is a string, it defines a directory to search.
 If an element is a variable symbol whose value is a string, that
 value defines a directory to search.
 If an element is a variable symbol whose value is a list, the
-value is used as a list of directories to search.")
+value is used as a list of directories to search."
+  :type '(repeat (choice (string)
+			 (sexp)
+			 (symbol))))

 (defun image-jpeg-p (data)
   "Value is non-nil if DATA, a string, consists of JFIF image data.
@@ -297,7 +300,11 @@
 		 (setq pathname (expand-file-name file element)))))
 	 ((consp element)
 	  (if (setq pathname (image-search-load-path file element))
-	      (setq found t))))))
+	      (setq found t)))))
+       ((or (and (consp element) (fboundp (car element)))
+	    (fboundp element))
+	(let ((string) (eval element))
+	  (and (stringp string) string))))
       (setq path (cdr path)))
     (if found pathname)))
--8<---------------cut here---------------end--------------->8---

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/

Re: About `image-load-path'

[Richard M. Stallman]

    Maybe image-load-path could also allow symbols.  Then one could make
    its last element the symbol `load-path', and thus it would be able to
    track changes of load-path.

That is how it works already.

Re: About `image-load-path'

[David PONCE]

>>So images are first searched in the Emacs data directory which is an
>>installation dependent directory. Wouldn't it be more relevant to
>>search in `load-path' first so it would be easier to overload standard
>>images?
> 
> 
> Can't you just your local directory to image-load-path ?

Yes it makes sense to let-bind `image-load-path' in my own code but it
is not so easy for libraries which are part of Emacs for example.  Do
you suggest that I change the default value of `image-load-path' in my
init file? So perhaps making `image-load-path' customizable would be a
good idea?

> I think there are some potentially wierd implications of searching
> load-path first.

I don't see them.  

Re: About `image-load-path'

[Kim F. Storm]

David PONCE <david.ponce@wanadoo.fr> writes:

>> I think there are some potentially wierd implications of searching
>> load-path first.
>
> I don't see them.  

If a user (accidentally) has e.g. both the current gnus (with icons in
etc/images) and an older version of gnus in load-path, the current
gnus might use the wrong icons.

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

Re: About `image-load-path'

[Jason Rumney]

Kim F. Storm wrote:

>If a user (accidentally) has e.g. both the current gnus (with icons in
>etc/images) and an older version of gnus in load-path, the current
>gnus might use the wrong icons.
>  
>
More likely the old gnus might use the correct icons, since site-lisp is 
listed first in the load-path.

Re: About `image-load-path'

[Chong Yidong]

David PONCE <david.ponce@wanadoo.fr> writes:

>>>So images are first searched in the Emacs data directory which is an
>>>installation dependent directory. Wouldn't it be more relevant to
>>>search in `load-path' first so it would be easier to overload standard
>>>images?
>> 
>> 
>> Can't you just your local directory to image-load-path ?
>
> Yes it makes sense to let-bind `image-load-path' in my own code but it
> is not so easy for libraries which are part of Emacs for example. 

Libraries that are part of Emacs ought to put the images in
etc/images.

Re: About `image-load-path'

[Richard M. Stallman]

    Yes it makes sense to let-bind `image-load-path' in my own code but it
    is not so easy for libraries which are part of Emacs for example.

Could you give an example of where you would want to do this
in the code of a library that is part of Emacs?

Chong Yidong wrote:

    Libraries that are part of Emacs ought to put the images in
    etc/images.

That is how this is intended to be used.

About `image-load-path'

[David PONCE]

Hello,

In image.el the new variable `image-load-path' is set to:

(list
 (file-name-as-directory (expand-file-name "images" data-directory))
 'data-directory
 'load-path)

So images are first searched in the Emacs data directory which is an
installation dependent directory. Wouldn't it be more relevant to
search in `load-path' first so it would be easier to overload standard
images?

(list
 'load-path
 (file-name-as-directory (expand-file-name "images" data-directory))
 'data-directory)

Sincerely,
David

Re: About `image-load-path'

[Kim F. Storm]

David PONCE <david.ponce@wanadoo.fr> writes:

> So images are first searched in the Emacs data directory which is an
> installation dependent directory. Wouldn't it be more relevant to
> search in `load-path' first so it would be easier to overload standard
> images?

Can't you just your local directory to image-load-path ?

I think there are some potentially wierd implications of searching
load-path first.


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