Update: This is now part of my
java-mode-plus Emacs extension.
Developing C in Emacs is a real joy, and it's mostly thanks to the
compile command. Once you have your Makefile — or SConstruct or
whatever build system you like — setup and you want to compile your
latest changes, just run
M-x compile, which will run your
build system in a buffer. You can then step through the errors and
C-x `, and Emacs will take you to them.
It's a very nice way to write code.
I use the compile command so much that I bound it to
C-k tends to be part of compile key
Until recently, I didn't have as nice of a setup for Java. Since they
generally force offensive IDEs onto me at work this wasn't something I
needed yet anyway, but I get to choose my environment on a new
project this time. If you're using Makefiles for some reason when
building your Java project, it still works out fairly well because
they're usually called recursively. It gets more complicated with Ant, where there is only one
top-level build file. Emacs' compile command only runs the build
command in the buffer's current directory.
I know three solutions to this problem. One is to provide the build
file's absolute path when
compile asks for the command
-f) option. You only
need to type it once per Emacs session, so that's not too bad.
ant -emacs -buildfile /path/to/build.xml
It's not well documented, but there is a
that can be given to Ant that will cause it to search for the build
file itself. This is even nicer than the previous solution. Just
remember to place it last, unless you give it the build filename
too. For example, if you wanted to run the
ant -emacs clean -find
To keep the actual call as simple as possible, I wrote a wrapper for
compile, and put a hook in
change the local binding. The wrapper,
searches for the build file the same way
-find would do.
So I can transparently keep using my muscle memory compile binding, I
set up the key binding in a hook,
Voila! Java works looks a little bit more like C.