Here are some tips and tricks on setting up Emacs.app on Mac OS X. These are based on my personal experience of using Emacs.app for the past 10 years or so; there may be better ways, but these work for me.
Call this script "emacs" and put it somewhere in your PATH (~/bin or /usr/local/bin):
Make sure the latest emacsclient binary is in your path:
ln -s /Applications/Emacs.app/Contents/MacOS/bin/emacsclient /usr/local/bin
# or ~/bin if you prefer
Call this script "ec" and put it somewhere in your PATH (~/bin or /usr/local/bin):
Add "alias emacs=ec" or "alias emacsclient=ec" to your ".bashrc". Or just use ec directly.
Add add this snippet to your .gitconfig:
If you want to use emacsclient, add this snippet instead:
The easiest way is to use the Customize interface: "M-x customize-group RET ns RET".
If you don't like Customize and want to do it manually, the following variables control the modifier keys:
Each variable can be set to 'control, 'meta, 'alt, 'super, or 'hyper.
In addition ns-alternative-modifier (and ns-option-modifier) can be set to 'none, which lets it get interpreted by the OS so it can be used to input special characters.
The ns-right-* variables are set to 'left by default which makes them the same as their left counterpart.
This site serves the binaries via SSL and while the binaries are not GPG signed, the application is code signed. You can verify the signature like this:
codesign -dvv /Applications/Emacs.app
Or, if you haven't installed emacs yet, but have mounted the disk image:
codesign -dvv /Volumes/Emacs/Emacs.app
Look for the following in the output:
Authority=Developer ID Application: Galvanix
Authority=Developer ID Certification Authority
Authority=Apple Root CA
"Galvanix" is my consulting partnership and is what I registered my Apple developer account under. If you see that, the binary is intact.