From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: New GNOME icons
Date: Tue, 14 Mar 2006 20:57:30 +0900 [thread overview]
Message-ID: <b4mbqw98cid.fsf@jpl.org> (raw)
In-Reply-To: <22907.1142318606@olgas.newt.com>
>>>>> In <22907.1142318606@olgas.newt.com> Bill Wohler wrote:
> By the way, Richard had a few comments about our
> image-load-path-for-library function. He didn't like that "path" was a
> symbol. He preferred to pass the value. Also, he didn't like it that we
> weren't always returning a list, such as when "path" was t. I think he's
> right. Indeed, fixing these things simplified the final cond to just:
> (nconc (list image-directory)
> (delete image-directory (copy-sequence (or path load-path))))))
> Note that we now document that the directory is first, so the "path ==
> t" feature can be achieved with (car (image-load-path-for-library ...)).
> I've made the changes that Richard suggested, but I'd like to get
> confirmation from you folks that they are OK with you too before
> committing them. At that time, you can copy the changes from
> image-load-path-for-library into gmm-image-load-path-for-library and
> remove your changes to gmm-defun-compat.
Well, I have currently no idea about that since I didn't follow
the whole story. But I have an unsophisticated doubt.
When Emacs didn't have new image files, I programmed my shell
script which builds and installs Gnus so that it installs image
files to the "/usr/local/share/emacs/etc/images/" directory, and
I added it to `image-load-path' as the first element. The
reason I did so is I don't want to modify image files that Emacs
provides though I want Gnus to display new icon images.
(The default directory in which Emacs' image files are
installed is "/usr/local/share/emacs/VERSION/etc/images/".
Normally Emacs doesn't care "/usr/local/share/emacs/etc/images/"
which I made.)
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.
> Is the plan to release Emacs 22, and then merge the Unicode stuff
> into the trunk immediately after that? The Unicode changes would be the
> major change to Emacs 23, right? I'm looking forward to that.
I don't know at all. Maybe RMS (or possibly Kenichi Handa) has
an answer. :)
next prev parent reply other threads:[~2006-03-14 11:57 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 [this message]
2006-03-14 17:58 ` Bill Wohler
2006-03-15 1:49 ` Katsumi Yamaoka
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=b4mbqw98cid.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).