geiser and chez talk to each other https://jao.io/cgit/geiser-chez/atom?h=0.1 2010-11-26T23:54:59Z 2010-11-26T23:54:59Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-26T23:54:59Z urn:sha1:b39fd77d8899bc7ff6608645afc9e2eb0eb0d33c We avoid using elisp's read for symbols, reading uninterned ones instead. And then, we cannot use symbols as keys in responses from scheme: we're using strings instead. 2010-11-26T01:29:25Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-26T01:29:25Z urn:sha1:f661d7c70bd04542d8bbb4da9c9f70b6d6c95791 When the symbol is imported and re-exported by a second module, we display its definition name and original module, besides the name of the module re-exporting it. 2010-11-25T00:30:48Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-25T00:30:48Z urn:sha1:acffa001cd9effa4a74261ac9b72e736b9b61937 We put the value of the identifier where it belongs, and add a missing period. Works, but geiser/doc.scm is in sore need of a refactoring. 2010-11-23T00:58:33Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-23T00:58:33Z urn:sha1:3b24e917fdfebc8df3fefbbcc747963eb4bbd126 We have a new "manual lookup" command, and Racket now displays a doc browser buffer for help with a button activating it. In the process, we've cleaned-up a little mess in geiser-eval.el and geiser-doc.el, and refactored the affected Racket modules. Next in line is providing manual lookup for Guile. 2010-11-21T15:12:41Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-21T15:12:41Z urn:sha1:f531c3e0f5afda77ada497d3932ea10502e22bdb 2010-11-21T02:50:41Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-21T02:50:41Z urn:sha1:8ebfa570ad6a722a831c53a0229464055bf227c3 Refreshing the cache on form evaluation (had been deactivated by error since the introduction of meta-commands). The current behaviour is not yet completely correct: if one evaluates a form in a modified buffer, geiser won't notice the new definition's signature, not even after the buffer is saved if one has gone around asking for autodoc before that. An improvement would be to make the cache sensitive to file write times, as suggested back in the day by Eli & Neil. 2010-11-21T00:56:02Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-21T00:56:02Z urn:sha1:1d725a8c087b66b2cd2c0e5006c376faf612d6ff We now display procedure signatures in module help, and keep a cache in Guile, using procedure properties. 2010-11-14T19:43:26Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-14T19:19:10Z urn:sha1:a07fcbb866082f533acbe89e028d05d4a3904b2a Spinning up from correct fontification of [else in this brave Racket world. I'm keeping the list of extra keywords lean and mean, but making it customizable in both Racket and Guile. 2010-11-13T01:07:19Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-13T01:07:19Z urn:sha1:1853b281918ea8c6e143ed1cfe1950189956d076 Inferior schemes weren't really a good idea, were they? With remote connections one can launch an external scheme to debug Geiser anyway. And everything is (ahem, will be) simpler when we add new implementations. 2010-11-12T22:21:02Z Jose Antonio Ortega Ruiz jao@gnu.org 2010-11-12T21:55:40Z urn:sha1:e070d76166d249695f1d2ee0269cc5c91537e0c9 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.