On Fri, Aug 14 2015, Federico Beffa wrote: > On Fri, Aug 14, 2015 at 12:05 AM, Jose A. Ortega Ruiz <[email protected]> wrote: >> >> Hi, >> >> On Thu, Aug 13 2015, Federico Beffa wrote: >> >>> Hi, >>> >>> I believe that Geiser is interfering with Emacs' own 'xscheme' >>> library. If I execute >>> >>> (require 'xscheme) >>> >>> then the command 'run-scheme' starts my MIT Scheme interpreter in a >>> '*scheme*' buffer. However, if I also >>> >>> (require 'geiser-install) >>> >>> then the command 'run-scheme' changes behavior. In particular it asks >>> me to choose scheme implementation, but it doesn't allow me to choose >>> the MIT scheme. >> >> Geiser does not redefine 'run-scheme', and i cannot reproduce the error >> you describe here. The functions defined by geiser are 'run-geiser', >> 'run-guile', 'run-chicken' and 'run-racket'. > > I know, and in fact C-h f run-scheme shows that the function doesn't > belong to Geise even after loading it. > But I've got the impression that Geiser modifies some underlying > functionality used by 'xscheme'.
Hmmm, it's not obvious to me how this could happen, but i'm now able to reproduce it (i was using cmuscheme's run-scheme instead of xscheme's before). Let me take a closer look!
