summaryrefslogtreecommitdiff
path: root/elisp/geiser-mode.el
diff options
context:
space:
mode:
authorJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-12 22:55:40 +0100
committerJose Antonio Ortega Ruiz <jao@gnu.org>2010-11-12 23:21:02 +0100
commit46d12e9318538dfab7c36415415b3e5f12b84b85 (patch)
treec2f77f5fa6649e9fdd02beb29d3cd8139d92b4f0 /elisp/geiser-mode.el
parentfe966fe13a6c65d7ea2dcd84544de7522789bedf (diff)
downloadgeiser-46d12e9318538dfab7c36415415b3e5f12b84b85.tar.gz
geiser-46d12e9318538dfab7c36415415b3e5f12b84b85.tar.bz2
Make do with a single connection
Separate connections for the REPL and Geiser commands was kind of neat, but it had the problem of synchronising the current namespace for both connections. A quick fix would have been to ask the scheme for the current namespace for every Geiser command in the REPL, but that, besides clunky, would add potentially prohibitive overhead for (real) remote connections. As it happens, using a single connection turned out to be not that difficult and relatively clean code-wise. We could even turn back to not use inferior schemes, and the net result of this refactoring would be the replacement of comint-redirect (which wasn't able to match the whole EOT token if it didn't arrive all at once) by transaction queues (which also makes geiser-connection's implementation cleaner). But using an inferior scheme has a dog-food value, and allows external processes to connect to the scheme being used by Geiser without further ado, which could be useful for debugging (although this is a lame excuse: nothing prevents you from starting a REPL server from emacs if you want). We'll see.
Diffstat (limited to 'elisp/geiser-mode.el')
0 files changed, 0 insertions, 0 deletions