Am 05.07.2007 um 17:03 schrieb stefan:
> $ open -a /Applications/Emacs.app/Contents/MacOS/Emacs
> $ open -a Emacs
>
> Both lines let the Emacs icon in the dock jump exactly once, but then
> no black triangle appears indicating that Emacs has started.
>
> Any other ideas?
>
Oh, sorry! I made a very big mistake: the correct alias has to be:
alias emacs="open -a /Applications/Emacs.app"
If you use the actual binary inside the application's bundle, then
some applications are not properly initialised. This can be a good
thing: you can launch such an application more than once! In case of
Carbon Emacsen it seems that they are a bit sensitive whether they
are launched as a real file (or hard-link, which both are
unambiguous) or as some symbolic link ...
Another thing is emacsclient. With a line
(server-start)
in ~/.emacs the running Emacs application can receive ELisp code or
file names from emacsclient. It might make more sense to launch
Carbon Emacs as a startup object and communicate to it via
emacsclient, which is /Applications/Emacs.app/Contents/MacOS/bin/
emacsclient.
You can read its man page in Emacs!
Could be the failure you observe comes from the fact that you have
the (application file or bundle) Emacs(.app) and also a file (or sym-
link) Emacs inside that application bundle. The Mac OS X launch
service might be confused from this. 'open Emacs.app' might give
better results (being clearer, less ambiguous) - but not for me: I
have a few "Emacs.app" objects on my volume. So I have to invoke
"open /path/to/each/Emacs.app."
--
Greetings
<]
Pete o __o |__ o recumbo
___o /I -\<, |o \ -\),-% ergo sum!
___/\ /\___./ \___...O/ O____.....`-O-'-()--o_________________
--~--~---------~--~----~------------~-------~--~----~
"Carbon Emacs" group mailing list.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/carbon-emacs?hl=en
-~----------~----~----~----~------~----~------~--~---
