[7276] in Athena Bugs

home help back first fref pref prev next nref lref last post

consider this a bug in (or suggestion for) emacs...

daemon@ATHENA.MIT.EDU (daemon@ATHENA.MIT.EDU)
Mon Mar 11 16:58:04 1991

Date: Mon, 11 Mar 91 16:57:53 -0500
From: Ken Raeburn <Raeburn@MIT.EDU>
To: bugs@MIT.EDU

I glanced at the C code and saw no way for a package to determine the
pathname it came from.  There are times (like this) when it is
desirable....

(Context: discuss.el needs to run another program in a subprocess; the
program is found in one of two places, depending on where the elisp
code is used from.  One is an experimental version, the other a
released version; they do have to (each) find the correct executable.)

Subject: Re: load paths in emacs discuss
Date: Sat, 9 Mar 91 14:41:54 -0500
From: Mark W. Eichin <eichin@ATHENA.MIT.EDU>
To: qjb@ATHENA.MIT.EDU
Cc: bug-sipb@ATHENA.MIT.EDU, bug-discuss@ATHENA.MIT.EDU

Agreed, it was clumsy (ie. it wasn't me :-) It's really to bad noone's
come up with a good way to install emacs scripts automatically (or
better yet, have a "pathname package came from" function!) so that the
*one* variable that gets changed (for the 3 places they get installed)
gets done right.
						_Mark_

home help back first fref pref prev next nref lref last post