|
| From: | David Reitter |
| Subject: | Re: Carbon Emacs won't start when installed in certain paths |
| Date: | Tue, 10 Apr 2007 17:56:40 +0100 |
On 10 Apr 2007, at 03:59, YAMAMOTO Mitsuharu wrote:
I think he is using Carbon Emacs with "self-contained" setting which puts subdirectories for runtime (lisp, etc, libexec, ...) below the Emacs.app directory so as to make the application bundle relocatable.
Yes, that's correct.
That requires some changes here and there. Though I just tried that, it may not be exhaustive and I'm not sure if it is safe to use ENCODE_FILE in init_callproc. Also, this kind of changes may not be appropriate at this stage.
I tried your patch and unfortunately, it does not fix the startup problem.
Error messages are the same.The good news is that I can start up an Emacs with -Q and -nw (as before, complaining about encoded-kb), but then, `load-file' works with a file that resides inside the offending path, which it didn't before.
| [Prev in Thread] | Current Thread | [Next in Thread] |