Gnus development mailing list
 help / color / mirror / Atom feed
From: Bill Wohler <wohler@newt.com>
Cc: mh-e-devel@lists.sourceforge.net, ding@gnus.org
Subject: Re: Modifying image-load-path/load-path
Date: Fri, 10 Mar 2006 15:09:36 -0800	[thread overview]
Message-ID: <87r759vqvj.fsf@olgas.newt.com> (raw)
In-Reply-To: <878xrzm20y.fsf@stupidchicken.com>

Chong Yidong <cyd@stupidchicken.com> writes:

> Bill Wohler <wohler@newt.com> writes:
>
>> We are also working to replace redundant code for locating our packages'
>> images and updating image-load-path (load-path in Emacs 21) with a
>> single function in image.el.
>>
>> Our question for you is this: should such a function actually modify the
>> image-load-path (as MH-E does now), or simply return a modified version
>> of image-load-path for use in a scoped variable copy of image-load-path
>> (as Gnus does now)?
>
> IMO, using a scoped copy is cleaner.  Is there any reason to modify
> the image-load-path permanently?

Thanks, Chong. I'm surprised you were the only one who replied. Since
both you and the Gnus project leaned towards a scoped variable, I took
that approach and checked in image-load-path-for-library just now.

Reiner, if you haven't done so already, it would be good to
deprecate/replace calls to mm-image-load-path and possibly
nnheader-find-etc-directory too.

-- 
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.

      parent reply	other threads:[~2006-03-10 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-20 23:11 Bill Wohler
2006-02-25 23:50 ` Chong Yidong
2006-02-26  1:52   ` Bill Wohler
2006-03-10 23:09   ` Bill Wohler [this message]

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=87r759vqvj.fsf@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=ding@gnus.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).