geiser/elisp, branch 0.1.3 emacs and scheme talk to each other https://jao.io/cgit/geiser/atom?h=0.1.3 2011-06-22T22:40:37Z Irrelevant compilation warning fix 2011-06-22T22:40:37Z jao jao@gnu.org 2011-06-22T22:40:37Z urn:sha1:b0d6c15ad6801fb46093c85aa59e772373ca81a9 Using called-interactively-p instead of interactive-p, if you have to know. The latter is deprecated as of Emacs 23.2, which the lowest version supported by Geiser. Avoid (read) breakage (fixes #33090) 2011-06-22T22:32:27Z jao jao@gnu.org 2011-06-22T22:32:27Z urn:sha1:4396a8cf2d27c03589a60e14c1eb95a3ba21fff8 Autodoc was firing while the REPL was waiting for input of a (read) call, causing all kinds of misbehaviour. We now inhibit autodoc on sending a form for evaluation and re-inhibit it once a prompt is read back again. Bug fix: don't confuse REPL buffers 2011-03-06T15:28:20Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-06T15:28:20Z urn:sha1:56e279b900535cf4c3b9d23a81124190592aaea2 We were not checking the implementation associated to a REPL buffer when reusing it, with much confusion ensued. Missing require form 2011-03-06T15:10:55Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-06T15:10:55Z urn:sha1:19f05d1355e19d79536b458f2eb723489eeff7d7 Elisp nit 2011-03-06T02:38:26Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-06T02:38:26Z urn:sha1:ab319cfffeaa7276dfe7bb2e8dea6480e84afff0 Nothing interesting, really. Fix for harmless elisp compilation warning 2011-03-06T02:33:09Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-06T02:33:09Z urn:sha1:035648caddbf000526027c032d0a61bf1abcc08c Bug fix: honour geiser-repl-use-other-window 2011-03-05T12:28:34Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-03-05T12:28:34Z urn:sha1:5846152ba151bbd9da1e361059dd1337d23506c2 Fix for the fix of the fix 2011-02-14T05:48:31Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-02-14T05:48:31Z urn:sha1:5aabaeb8e672ae6799166708166ecd30cb6c716d Fix for the fix 2011-02-14T05:25:59Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-02-14T05:25:59Z urn:sha1:a864aa029f751416da37c8b3a02fad4c8558cae7 Guile REPL: bug fix: correctly track debugging status 2011-02-14T05:10:50Z Jose Antonio Ortega Ruiz jao@gnu.org 2011-02-14T05:10:50Z urn:sha1:ba932f095a7078d602802940f326216e85a847ce We weren't tracking the "enter debugger" event correctly, and all evaluations in debug mode were failing. There's still (at least) another bug, because error navigation in backtraces seems broken.