Luke Gorrie lgorrie@common-lisp.net writes:

How about now? I changed permissions on the doc/ directory.

Works fine now. Thanks,

Paolo

Helmut Eller e9626484@stud3.tuwien.ac.at writes:

Some things should probably be explained a bit more detailed. E.g., how the buffer package is determined and in which package the strings are read. Also the role of the *inferior-lisp* buffer might be confusing to newbies.

True. I'll write a proper introduction to `slime-mode' to cover this sort of stuff.

BTW, are we still trying to get rid of inf-lisp or do we keep it forever? The primary annoyance are all the unwanted keybindings, but otherwise it seems to work quite well.

I reckon it's still pulling its weight for debugging and suchlike, so I'm happy enough keeping it m'self.

It is a bummer that it hacks its bindings into lisp-mode instead of being a minor-mode. On the other hand, I've had some hassle with slime being a minor-mode - clobbering keybindings of more important minor modes (in 'emerge' buffers). Do you know any fix for that?

-Luke

Helmut Eller e9626484@stud3.tuwien.ac.at writes:

I wonder if this is our of emerge's fault. It seems that emerge only puts itself into minor-modes-list to get an entry in the modeline and it doesn't use minor-mode-map-alist, but some custom local-map. This would explain why the SLIME bindings override the emerge keys, since key lookup always looks at the minor-mode-map-alist before searching in the local-map. Do the problems persist if you turn SLIME off?

Turning slime-mode off does fix it, so it's not a big problem. And yeah, it does seem likely to be their fault, since there's nothing exotic about our having a minor mode that binds some keys.

-Luke