From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: New GNOME icons
Date: Wed, 15 Mar 2006 10:49:38 +0900 [thread overview]
Message-ID: <yamaokairqgeatp.fsf@jpl.org> (raw)
In-Reply-To: <1183.1142359136@olgas.newt.com>
>>>>> In <1183.1142359136@olgas.newt.com> Bill Wohler wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> wrote:
[...]
>> My doubt is that there seems to be no way to tell the
>> `(gmm-)image-load-path-for-library' function that my image files
>> are in "/usr/local/share/emacs/etc/images/". Of course, it is
>> not a matter since Emacs provides new image files now, though.
> Just add your directory to image-load-path (or load-path if
> image-load-path isn't bound) before calling the function and it will be
> found, assuming that the image passed to image-load-path-for-library is
> in your directory. This is what the Debian MH-E package does in its
> site-init.
I exactly did so. However, `image-load-path-for-library'
doesn't take notice of
"/usr/local/share/emacs/etc/images/gnus/toggle-subscription.xpm"
if
"/usr/local/share/emacs/22.0.50/etc/images/gnus/toggle-subscription.xpm"
exists. It suggests there's no way that she uses her favorite
images instead of the ones Emacs provides.
image-load-path
=> ("/usr/local/share/emacs/etc/images/"
"/usr/local/share/emacs/22.0.50/etc/images/"
data-directory
load-path)
(file-exists-p
"/usr/local/share/emacs/etc/images/gnus/toggle-subscription.xpm")
=> t
(file-exists-p
"/usr/local/share/emacs/22.0.50/etc/images/gnus/toggle-subscription.xpm")
=> t
(let ((dirs (image-load-path-for-library
"gnus"
"gnus/toggle-subscription.xpm"
nil t)))
(or (member "/usr/local/share/emacs/etc/images/" dirs)
(member "/usr/local/share/emacs/etc/images" dirs)))
=> nil
next prev parent reply other threads:[~2006-03-15 1:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 0:18 Bill Wohler
2006-03-10 23:15 ` Bill Wohler
2006-03-10 23:56 ` Reiner Steib
2006-03-11 1:23 ` Bill Wohler
2006-03-11 1:29 ` Miles Bader
2006-03-11 12:48 ` Reiner Steib
2006-03-11 2:12 ` *image-load-path-for-library update Bill Wohler
2006-03-11 11:33 ` Reiner Steib
2006-03-11 22:53 ` Bill Wohler
2006-03-12 1:43 ` Bill Wohler
2006-03-12 2:00 ` Bill Wohler
2006-03-13 11:52 ` New GNOME icons Katsumi Yamaoka
2006-03-13 16:56 ` Bill Wohler
2006-03-14 5:32 ` Katsumi Yamaoka
2006-03-14 6:43 ` Bill Wohler
2006-03-14 11:57 ` Katsumi Yamaoka
2006-03-14 17:58 ` Bill Wohler
2006-03-15 1:49 ` Katsumi Yamaoka [this message]
2006-03-15 7:34 ` Katsumi Yamaoka
2006-03-15 7:58 ` Katsumi Yamaoka
2006-03-16 1:41 ` gmm-image-load-path-for-library redux (was: New GNOME icons) Bill Wohler
2006-03-16 2:04 ` gmm-image-load-path-for-library redux Katsumi Yamaoka
2006-03-16 7:24 ` Katsumi Yamaoka
2006-03-16 8:05 ` Bill Wohler
2006-03-16 17:41 ` Bill Wohler
2006-03-16 1:39 ` New GNOME icons Katsumi Yamaoka
2006-03-14 15:16 ` Reiner Steib
2006-03-14 19:29 ` Bill Wohler
2006-03-14 21:00 ` Reiner Steib
2006-03-14 21:35 ` Bill Wohler
2006-03-15 8:58 ` Reiner Steib
2006-03-15 12:10 ` Reiner Steib
2006-03-15 15:42 ` Bill Wohler
2006-03-15 16:40 ` defvars at compile time (was: New GNOME icons) Reiner Steib
2006-03-15 16:49 ` defvars at compile time Bill Wohler
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=yamaokairqgeatp.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).