Hi Helmut,
Helmut Eller heller@common-lisp.net writes:
- Stefan Kamphausen [2005-09-27 14:01+0200] writes:
If you are interested in using this code in -say- slime.el I'll pass copyright to you (as I state in the header of the attached file). If you prefer to receive a patch to slime.el I can do that, too. Just tell me.
Nice idea!
:-)
Yes, I think we should add this or something like this.
And again: :-)
I wonder if we need explicit commands to load/save the history or if we should simply load it at startup and append the current line to the file every time when return gets pressed.
That would be fine if the connection is always local. What would happen to a history with a REPL that is connected to a remote lisp? Write to local disc or pass it to the remote machine. If the latter it *might* be a performance problem. I can't tell because only work locally for the moment.
Since my code is very new and I haven't used it much, I think that someone will come up with a situation when it's not very intuitive...
I guess, I wouldn't bother to save the history if I need to invoke an explicit command.
What I currently use is a defadvice in my configuration files around slime-quit-lisp:
(defadvice slime-quit-lisp (around slime-quit-lisp-with-history activate) (slime-repl-save-merged-history) ad-do-it)
Regards Stefan Kamphausen