geiser-chez/scheme/racket, branch 0.1.4 geiser and chez talk to each other https://jao.io/cgit/geiser-chez/atom?h=0.1.4 2011-11-26T06:11:26Z Racket: capturing and displaying standard error during evaluation 2011-11-26T06:11:26Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-11-26T06:11:26Z urn:sha1:9857c254979e7c43a3f432c1927a168d6437398c This bugs was exposed by using rackunit, where all the output of, say, check-eq? was lost for good (it was being sent to the stderr black hole). Hat tip Grant Retkke. Leftover code from the previous patch removed 2011-08-20T16:15:07Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-08-20T16:15:07Z urn:sha1:51982d010fd4a44f93d6df3eceda6ffcebe1dbc2 Racket: eval geiser-eval's apply arguments properly 2011-08-20T14:29:46Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-08-20T01:31:54Z urn:sha1:1627471032647e6a13149242ad9547b5124c1c4f As Stanisław Halik reported, autodoc was receiving a mlist (instead of a list) as its argument when invoked in an R5RS context. Turns out we were evaluating geiser-eval's arguments in the wrong context (the procedure being applied and the arglist belong to the same namespace). Racket: use the proper interaction port for input (#32844) 2011-03-21T11:30:11Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-21T11:30:11Z urn:sha1:04902b39229eafdfa41e2c1d5a9857133f53805d Thanks to Caleb Reach. We were using current-input-port, which is not the right port in graphical environments. Racket: geiser-add-to-load-path implemented 2011-03-06T02:18:43Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-06T02:18:43Z urn:sha1:98374c61cc6de60f2fa2912ee9b5e3d199477ab7 And we take the chance to lightly document the existence of this new command in the user manual. Racket: no errors ,entering an R5RS module 2011-02-27T12:14:30Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-02-27T12:14:30Z urn:sha1:68a4e69aca1f8a84330def1ee24b2da6243419c0 The catch here is that one cannot use #%variable-reference inside an R5RS module, and, as a consequence, namespace->module-path-name was failing badly. The solution is to take note of the module name being entered before hand, and use that name in case of error (we could actually use that name always, but then cheaters using Racket's enter! would see an inconsistent name (which probably they deserve)). Racket: ',enter "foo"' as a synonym of ',enter (file "foo")' 2011-01-09T21:53:27Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-01-09T21:40:11Z urn:sha1:e1673221200c35bdacffebbcc26c2e562080a9fd No more interning in the scheme reader 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. Racket: more information in symbol documentation 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. Document browser improvements, and Racket using them 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.