-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to run emacs from command line? #57
Comments
Using an alias should work: #!/bin/sh
/Applications/Emacs.app/Contents/MacOS/Emacs "$@" I'm not going to close this bug though, because I think using a symlink should work. The launcher script should be able to detect that and act appropriately. |
Thanks! That works...
…On Sun, Nov 27, 2016 at 7:01 PM David Caldwell ***@***.***> wrote:
Using an alias should work: alias
emacs=/Application/Emacs.app/Contents/MacOS/Emacs. Of course that only
works if you are typing emacs into a shell. If you want other programs to
be able to launch Emacs (maybe it's in your EDITOR env var, for
instance), you need to do something else. I use a little stub shell script
(as described here <https://emacsformacos.com/tips>):
#!/bin/sh
/Applications/Emacs.app/Contents/MacOS/Emacs "$@"
I'm not going to close this bug though, because I think using a symlink
*should* work. The launcher script should be able to detect that and act
appropriately.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#57 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA7l11ZInqYCY0icxEm6oFMWkQgXH5HSks5rCjXwgaJpZM4K9QtW>
.
|
I installed emacs 25.1.1 using
brew cask install emacs
. All went well (I can run it by launching from the finder) until I tried to create a symlink to run emacs from the command line. I triedand when I run it I get a popup that says
This application will not run on your computer. Sorry!
I discovered that when run from the finder it actually uses
Emacs-x86_64-10_9
(I'm on Yosemite) so I triedand I get:
What is the secret?
thanks
The text was updated successfully, but these errors were encountered: