3 ms·
A more important question for me: How is this different from building Emacs out of MacPorts? I interact with Emacs solely through a terminal window, and so don
by ubernostrum 17y ago
A more important question for me:
How is this different from building Emacs out of MacPorts? I interact with Emacs solely through a terminal window, and so don't need or want a GUI version.
- philwelch 17y agoMy Mac OS X comes with emacs and vim already if you're using the terminal. I thought they all did.
- ubernostrum 17y agoYes, but it usually lags a bit behind the current versions (as all operating-system packages do). So I end up building a more recent one from MacPorts anyway.
- __david__ 17y agoThere are 2 ways it is different: 1) It is a self contained .app file and generally goes in your /Applications folder which means you have to go out of your way to get it to launch from the terminal by simply typing "emacs". I put this little sh script in my path somewhere: #!/bin/sh /Applications/Emacs.app/Contents/MacOS/Emacs "$@" 2) Since it isn't a text only Emacs, launching it from the command line still creates a bouncy Emacs icon on your dock and gives it its own window and menu bar. "emacs -nw", as usual, takes you straight to text mode without leaving the terminal.