From: Chong Yidong <cyd@stupidchicken.com>
Cc: mh-e-devel@lists.sourceforge.net, ding@gnus.org
Subject: Re: Modifying image-load-path/load-path
Date: Sat, 25 Feb 2006 18:50:21 -0500 [thread overview]
Message-ID: <878xrzm20y.fsf@stupidchicken.com> (raw)
In-Reply-To: <7620.1140477119@olgas.newt.com> (Bill Wohler's message of "Mon, 20 Feb 2006 15:11:59 -0800")
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?
next prev parent reply other threads:[~2006-02-25 23:50 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 [this message]
2006-02-26 1:52 ` Bill Wohler
2006-03-10 23:09 ` 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=878xrzm20y.fsf@stupidchicken.com \
--to=cyd@stupidchicken.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).