home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.emacs.help
- Path: sparky!uunet!stanford.edu!ames!sun-barr!cs.utexas.edu!mercury.unt.edu!sol.acs.unt.edu!amos
- From: amos@sol.acs.unt.edu (Amos A. Gouaux)
- Subject: modification of load-path during build?
- Message-ID: <amos.713813003@sol.acs.unt.edu>
- Sender: usenet@mercury.unt.edu (UNT USENet Adminstrator)
- Organization: University of North Texas
- Date: Fri, 14 Aug 1992 17:23:23 GMT
- Lines: 26
-
- i'm considering making an alteration to the load-path when building
- emacs. i would like to have two directories specified, "../lisp/local"
- and "../lisp", in that order. the first directory in the search path
- would be for locally added/modified code. i thought this would be
- a tidy way to prevent these files from being inadvertently blown away
- during future installs. i was also thinking about putting "default.el"
- there too since it tends to be modified to incorporate local changes.
-
- can folks advise me as to whether or not this would be sound. where
- would be the most practical place to modify the load-path? in
- "paths.h"? in "site-init.el"? somewhere in the Makefile? i've been
- using make to build emacs - wouldn't that cause the definitions in
- "paths.h" to be lost? or should i just do the alteration in the
- regular "default.el" before anything else is done?
-
- also, why is it that "../info/dir" gets blown away during an install.
- if i'm not mistaken, aren't folks supposed to add info file packages
- underneath this root? should there be a "dir.local" as well?
-
- advice/tips/suggestions would be grately appreciated.
-
- a.
-
- --
- amos@unt.edu Amos A. Gouaux (817) 565-4161
- -= Academic Computing Services, University of North Texas, Denton, TX, USA. =-
-