11–20 of 66 posts
Scroll down to section 'Build from source' - note the comment to build from the 'nextstep' directory. I just followed the instructions in 'nextstep/INSTALL')
This is working for me, so far... a good way to get a 'vanilla' install.
http://bc.tech.coop/blog/081205.html
They are skewed to Clojure development, but you may be able to pick out a few tips.
http://github.com/jimweirich/emacs-setup/tree/master
Also, a starter emacs kit for rubyists:
I agree that the option key is no good as Meta - Cmd is Meta in my setup.
I absolutely override the Mac keybindings. I like having M-Q as fill-paragraph, and I found that other useful commands were being hijacked by useless OS X Text Services (like M-> for end of buffer got stolen by OmniOutliner)
I have a large 1920x1200 display that I tend to use with one emacs frame maximized, and some arrangement of windows inside that frame - most often I have a full height window on the left, and two half-height windows on the right. Sometimes I use three columns of windows, and other times four equal-sized windows makes sense.
One of those windows is almost always running zsh inside ansi-term (M-x ansi-term). Some prefer shell-mode, but I think ansi-term and zsh are more useful. I don't think shell-mode and zsh cooperate too well.
Most of my work is done in python, and I just started using pymacs and ropemacs, which seem useful. Notes on them are here: http://www.enigmacurry.com/2008/05/09/emacs-as-a-powerful-py...
I bind Option to Meta in Terminal.app and that works very well.
I have the option key (windows key on this keyboard) mapped to Hyper. I use Hyper to navigate around emacs. H-(n|p|b|f) move up, down, left, or right one window in a frame
H-(N|P|B|F) change the size of the current window height/width
other hyper bindings open apps that I use regularly (shell, anything, sql)
I use Terminal-based Emacs exclusively. Couldn't stand all the "distractions" (bells and whistles) of Aquamacs. But, more importantly, with this mode I can use Emacs everywhere, including my servers over ssh, with exactly the same setup. I bind Option to Meta in Terminal.app and that works very well.
I use Terminal-based Emacs exclusively. Couldn't stand all the "distractions" (bells and whistles) of Aquamacs. But, more importantly, with this mode I can use Emacs everywhere, including my servers over ssh, with exactly the same setup. I bind Option to Meta in Terminal.app and that works very well.
My config is at http://www.github.com/marten/emacs.d/ It contains a couple of useful fixes (such as Cocoa apps not getting the PATH var from the shell). It's got plenty comments. I should try turning more stuff into autoloads, I'm finding it on the slow side to start up right now.