When a buffer has a racket-repl-buffer-name already set to some value and that REPL buffer is visible, calling racket-repl causes a new REPL buffer to be created instead of visiting the existing one for that buffer.
Btw, this is in the context of #628 where we set the REPL buffer name at the time of creation of the scratch buffer, and then, attempting to visit the REPL buffer using racket-repl causes this to happen. I unfortunately haven't had much of a chance to work on this but I've been occasionally chipping away at it and with any luck we'll have something usable in the not-too-distant future 🙂
When a buffer has a
racket-repl-buffer-name
already set to some value and that REPL buffer is visible, callingracket-repl
causes a new REPL buffer to be created instead of visiting the existing one for that buffer.It looks like the issue is that calling
racket-repl
overwrites any existing buffer-local value forracket-repl-buffer-name
.Btw, this is in the context of #628 where we set the REPL buffer name at the time of creation of the scratch buffer, and then, attempting to visit the REPL buffer using
racket-repl
causes this to happen. I unfortunately haven't had much of a chance to work on this but I've been occasionally chipping away at it and with any luck we'll have something usable in the not-too-distant future 🙂