Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: New GNOME icons
Date: Tue, 14 Mar 2006 14:32:29 +0900	[thread overview]
Message-ID: <b4mr755zj4i.fsf@jpl.org> (raw)
In-Reply-To: <3861.1142268982@olgas.newt.com>

>>>>> In <3861.1142268982@olgas.newt.com> Bill Wohler wrote:

> Katsumi Yamaoka <yamaoka@jpl.org> wrote:

>>>>>>> In <v9fylp4zwh.fsf@marauder.physik.uni-ulm.de>
>>>>>>>	Reiner Steib wrote:
>>
>>> [1]	* gmm-utils.el (gmm-image-load-path-for-library): Return single
>>> 	directory if path is t.  Add no-error.
>>
>> Because of the `no-error' argument[1], I needed to modify the
>> `gmm-defun-compat' macro as follows

> Why? The arguments to *-defun-compat shouldn't make any difference. What
> problems were you seeing?

I'm sorry in the insufficient explanation.

The specification of the `image-load-path-for-library' function
contained in Emacs 23 that I had checked out on yesterday
morning (in Japan) was:

(image-load-path-for-library LIBRARY IMAGE &optional PATH)

It caused the `wrong-number-of-arguments' error since Gnus
specifies the fourth argument NO-ERROR to the
`gmm-image-load-path-for-library' function which is an alias to
`image-load-path-for-library'.  So, I had to modify the macro so
as to use the one that has been defined in gmm-utils.el.  But
now the problem is solved because image.el contained in Emacs 23
has been synch'd with the Emacs CVS trunk (i.e., Emacs 22.0.50).

>>                                     since I'm using Emacs 23.

> What's that?

Emacs 23 is being developed in the `emacs-unicode-2' branch of
the Emacs CVS repository.  It fully uses Unicode internally for
multilingual text, and merges the changes made in the trunk.
(You can check it out using the `-r emacs-unicode-2' option).

>> It will become unnecessary soon (when the `emacs-unicode-2'
>> branch is synch'd with the trunk), though.

> Please document that.

> Your patch is completely undecipherable to me. I'd like to see some
> documentation regarding the motivation for it, as well as what it is
> doing.

I presented what is needed to generalize the `gmm-defun-compat'
more, though it is not necessary for the moment.



  reply	other threads:[~2006-03-14  5:32 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 [this message]
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
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=b4mr755zj4i.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).