Am 09.10.2007 um 13:01 schrieb Adrian Robert: > Peter, does this make your local-lisp-path patch unnecessary, do > you think?
No. I was trying to introduce (one) more (helpful) configure option (s) to the compile script. The patch for nsterm.m only corrects the order in which the built-in paths are searched. A different approach would be to teach configure the default load- paths for each system for which it is being configured. On Mac OS X it is something like /Library/Application Support/Emacs and ~/Library/ Application Support/Emacs, but then it's not sure whether and which subdirectories there would be searched for ELisp files. What I am also missing is a change in general behaviour. When any GNU Emacs variant is launched from inside emacs/src, the ELisp in the source trees shadows (away) the system's ELisp installation, so that my calendar is showing strange religious holidays and the week starts with Sunday instead of the secular (?) Monday. But that's more the topic for a bug report ... -- Greetings Pete The human brain operates at only 10% of its capacity. The rest is overhead for the operating system. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Emacs-app-dev- mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emacs-app-dev-
