<philweb>
Does a mechanism exist to have slime maintain multiple independent histories? (i.e. I'd like to maintain separate repl histories per instance: 1) local ccl 2) local sbcl 3) remote sbcl etc)
Colleen has quit [*.net *.split]
epony has quit [*.net *.split]
epony has joined #slime
epony has quit [Max SendQ exceeded]
epony has joined #slime
Colleen has joined #slime
epony has quit [Remote host closed the connection]
epony has joined #slime
edgar-rft has quit [Quit: Leaving]
_whitelogger has joined #slime
_whitelogger has joined #slime
edgar-rft has joined #slime
edgar-rft has quit [Quit: Leaving]
<luis>
philweb: not at the moment. That might be nice, yes. Although a unified history is probably a better default.
<philweb>
@luis: thanks, just wanted to make sure I wasn't missing something. Agreed that the current behavior is a good default. When dealing with multiple simultaneous instances on different machines it can get tedious.
philweb has quit [Ping timeout: 245 seconds]
scymtym has quit [Read error: Connection reset by peer]