Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill Wohler <wohler@newt.com>
Subject: Re: Sharing mail icons between MH-E and Gnus
Date: Mon, 20 Feb 2006 14:53:10 -0800	[thread overview]
Message-ID: <6909.1140475990@olgas.newt.com> (raw)
In-Reply-To: Reiner Steib's message of Mon, 20 Feb 2006 22:19:47 +0100. <v964n9ybgs.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> I don't like that `mh-image-load-path' changes the variables
> `load-path' or `image-load-path'.

I'm not sure I agree. Taking this argument to an extreme conclusion,
both load-path and image-load-path would always be empty. Leaving the
path to our images on these paths makes it more clear to the user (or
developer) where the images came from, if that needs to be discovered.
It's also conceivable that using a temporary load-path/image-load-path
might invalidate image caching schemes.

>                                    Assume you have unbundled versions
> of Gnus and MH-E installed using Emacs 21. Which path should win, if
> we both use the same variable?

And what if the user adds his own images to image-load-path (if he
defined a theme, if you will) and expects to see his images rather than
yours? Since you didn't leave your path on the image-load-path, he would
be confused since he wouldn't see where they came from.

Hmmm, this argues that we would want prepend the default Emacs path
(since a newer Gnus/MH-E package might have newer images than the one
distributed with an old version of Emacs) and append to any user-defined
paths (since the user is always right). Is that possible?

At any rate, since we're coordinating now, those icons will probably be
the same anyway, so I don't think that this will be much of a problem.

> (defmacro gmm-defun-compat (name function arg-list &rest body)

We've borrowed so much from Gnus, I'd be tickled pink if Gnus borrowed
from MH-E ;-).

> (defun gmm-image-load-path (library &optional image path)

For the generalized function, we might want to make IMAGE non-optional
so that we don't have MH-E and Gnus icons in the code.

>   ;; Return augmented `image-load-path' or `load-path'.
>   (cond ((and path (symbolp path))
> 	 (nconc (list gmm-image-load-path) (symbol-value path)))
> 	(t
> 	 (nconc (list gmm-image-load-path) load-path))))

Now it's my turn not to like the code ;-). This doesn't use
image-load-path if it exists. It can add the image directory even if it
already exists on path.

I was going to argue against the path argument, but it would be
consistent with image-search-load-path. I think it's a good idea,
however, to return the modified list.

I guess the big question is whether to modify image-load-path
(load-path) or not. It would be good for a few others to weigh in. It
would be good to solicit opinions from the folks on emacs-devel too.
I'll do that.

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and MH-E. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

  reply	other threads:[~2006-02-20 22:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1EQxwu-00028T-D0@mail.sourceforge.net>
     [not found] ` <28928.1129483226@olgas.newt.com>
2005-10-17 13:27   ` Sharing mail icons between MH-E and Gnus (was: debian changelog,1.39,1.40 control,1.29,1.30 dirs,1.2,1.3 emacsen-install,1.5,1.6 emacsen-startup,1.12,1.13 rules,1.12,1.13) Reiner Steib
2005-10-17 15:32     ` Sharing mail icons between MH-E and Gnus Bill Wohler
2006-01-19 21:37       ` Reiner Steib
2006-01-23 17:46         ` Bill Wohler
2006-02-19  2:40         ` Bill Wohler
2006-02-20  1:26           ` Reiner Steib
2006-02-20 19:57             ` Bill Wohler
2006-02-20 22:04               ` Reiner Steib
2006-02-21  0:30                 ` Bill Wohler
2006-02-21 11:37                   ` Icons for frequently used sort commands (was: Sharing mail icons between MH-E and Gnus) Reiner Steib
2006-02-21 22:22                     ` Bill Wohler
2006-02-22  0:30                       ` Icons for frequently used sort commands Reiner Steib
2006-02-20 15:58           ` Sharing mail icons between MH-E and Gnus Reiner Steib
2006-02-20 21:23             ` Adam Sjøgren
2006-02-21 11:30               ` Reiner Steib
2006-02-21 22:11                 ` Bill Wohler
2006-02-22  0:30                   ` Reiner Steib
2006-02-22  5:09                     ` Bill Wohler
2006-02-22  6:43                     ` Adam Sjøgren
2006-03-06 16:46                     ` Bill Wohler
2006-03-06 19:15                       ` Reiner Steib
2006-03-06 21:40                         ` Bill Wohler
2006-03-06 23:21                           ` Reiner Steib
2006-03-07  0:06                             ` Bill Wohler
2006-02-20 21:19           ` Reiner Steib
2006-02-20 22:53             ` Bill Wohler [this message]
2006-02-21 21:22               ` Reiner Steib
2006-02-21 22:29                 ` 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=6909.1140475990@olgas.newt.com \
    --to=wohler@newt.com \
    /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).