| I've been doing a lot of Lisp at work lately, and finding myself frustrated with SLIME, the Superior Lisp Interaction Mode for Emacs, which is the standard way of editing Lisp programs. It's nothing major - just some irritations here and there with how some of the commands work. For example: if you have a function named FOO and you want to find out where it's used, you use C-c C-w C-c (slime-who-calls). This opens a window with a list of the functions that use FOO, and pressing Enter on any of the entries on the list opens the associated file and highlights the right line. But to actually edit the line, you have to press C-x o (other-window). This is not What The User Expects (for certain values of User, ie me). So every time I do it, I find myself stuck in a window I don't want. And when I compile and get errors, I get a highly detailed and cryptic display of the complete stack trace, but no indication of the line and file that caused the error. And so on. It's all minor, but over a day of programming, especially in an office full of interruptions and distractions, it adds up.
I think the answer is obvious: it's time I rewrote some of the underlying commands and adjusted my Emacs to suit me.
(What -- did you think I was going to give up and use Visual Studio or something? Bah! Emacs means never having to say you're annoyed... for very long.) |