[slime-devel] features from ILisp I miss in slime
Hello all, I've just tryed slime, after years of ILisp use, and I feel great! Slime is definitely a step ahead of ILisp. However, there some features I was used to in ILisp, and that I miss in slime. Maybe some of them are configurable, maybe others are not. Here goes my list: - there are a list of key bindings that can be seen after a C-h m in a Lisp Slime mode, which do not work (e.g., C-c C-a, C-c C-c, etc.) Some of them have different key bindings in Slime, while others follow a distinct functional scheme (e.g., showing arguments as you type, which works fine in slime). - in Lisp Slime mode a RET does not auto-indent the next line. It'd be useful to have auto-identation, so that we could save a TAB everytime we write a new line of LISP. - in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)? Cheers, Rodrigo -- *** Rodrigo Martins de Matos Ventura <yoda@isr.ist.utl.pt> *** Web page: http://www.isr.ist.utl.pt/~yoda *** Teaching Assistant and PhD Student at ISR: *** Instituto de Sistemas e Robotica, Polo de Lisboa *** Instituto Superior Tecnico, Lisboa, PORTUGAL *** PGP fingerprint = 0119 AD13 9EEE 264A 3F10 31D3 89B3 C6C4 60C6 4585
Rodrigo Ventura <yoda@isr.ist.utl.pt> writes:
- in Lisp Slime mode a RET does not auto-indent the next line. It'd be useful to have auto-identation, so that we could save a TAB everytime we write a new line of LISP.
I add (local-set-key "\C-m" 'newline-and-indent) to my Lisp mode-hook.
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
Why is it impractical? Zach
On Tue, 23 Nov 2004 20:19:02 +0000, Rodrigo Ventura <yoda@isr.ist.utl.pt> wrote:
Hello all,
I've just tryed slime, after years of ILisp use, and I feel great! Slime is definitely a step ahead of ILisp.
However, there some features I was used to in ILisp, and that I miss in slime. Maybe some of them are configurable, maybe others are not. Here goes my list:
- there are a list of key bindings that can be seen after a C-h m in a Lisp Slime mode, which do not work (e.g., C-c C-a, C-c C-c, etc.) Some of them have different key bindings in Slime, while others follow a distinct functional scheme (e.g., showing arguments as you type, which works fine in slime).
- in Lisp Slime mode a RET does not auto-indent the next line. It'd be useful to have auto-identation, so that we could save a TAB everytime we write a new line of LISP.
See my recent post for code which will not only auto-indent, but also show you the argument list of the current function, similar to when you press space.
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
This can be rebound easily, but personally I rather like M-p. I don't use the arrow keys much.
Rodrigo Ventura <yoda@isr.ist.utl.pt> writes:
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
Hmmm. M-p is consistent with shell mode which makes me very happy. I'm annoyed at any command-line kind of thing in Emacs that doesn't follow that convention. -Peter -- Peter Seibel peter@javamonkey.com Lisp is the red pill. -- John Fraser, comp.lang.lisp
"Peter Seibel" <peter@javamonkey.com> wrote in message news:m3wtwcm11l.fsf@javamonkey.com...
Rodrigo Ventura <yoda@isr.ist.utl.pt> writes:
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
Hmmm. M-p is consistent with shell mode which makes me very happy. I'm annoyed at any command-line kind of thing in Emacs that doesn't follow that convention.
You mean Eshell? [Up] is bound the same as M-p by default, and you have to use C-p and C-n to move the cursor vertically. In fact, I'd like it to be the same in my slime-repl, by default. [Up] is for history as well as M-p, and C-p is for cursor movement. Chris Capel
Rodrigo Ventura <yoda@isr.ist.utl.pt> writes:
- there are a list of key bindings that can be seen after a C-h m in a Lisp Slime mode, which do not work (e.g., C-c C-a, C-c C-c, etc.) Some of them have different key bindings in Slime, while others follow a distinct functional scheme (e.g., showing arguments as you type, which works fine in slime).
We have generally overridden the inf-lisp/ilisp bindings so they are not supposed to work. This is because they talk directly to *inferior-lisp* and aren't consistent with SLIME's style. It was confusing before when people would accidentally use non-SLIME commands thinking they belonged to SLIME and get weird results. `C-c C-a' we have currently reserved for future use; C-c C-c should compile the definition at point.
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
I added bindings for C-{up,down} since comint-mode also provides these in addition to M-{n,p}. Cheers, Luke
Luke Gorrie wrote:
Rodrigo Ventura <yoda@isr.ist.utl.pt> writes:
- there are a list of key bindings that can be seen after a C-h m in a Lisp Slime mode, which do not work (e.g., C-c C-a, C-c C-c, etc.) Some of them have different key bindings in Slime, while others follow a distinct functional scheme (e.g., showing arguments as you type, which works fine in slime).
We have generally overridden the inf-lisp/ilisp bindings so they are not supposed to work. This is because they talk directly to *inferior-lisp* and aren't consistent with SLIME's style.
It was confusing before when people would accidentally use non-SLIME commands thinking they belonged to SLIME and get weird results.
`C-c C-a' we have currently reserved for future use; C-c C-c should compile the definition at point.
- in the REPL loop M-p is not quite pratical; couldn't you use for instance C-up for last expression entered (similar to ILisp)?
I added bindings for C-{up,down} since comint-mode also provides these in addition to M-{n,p}.
Cheers, Luke
In slime 1-0 the menu bar shows M-p as the shortcut for both previous and next input(I think it means the same as command). But the shortcut key works as the previous command(input). The options in the menu works fine. What is the shortcut key for the next command. -- Surendra Singhi www.public.asu.edu/~sksinghi
participants (7)
-
Chris Capel -
Luke Gorrie -
Peter Seibel -
Rodrigo Ventura -
Surendra Singhi -
Svein Ove Aas -
Zach Beane