| commit | 0f66c250245af1348a3ee5a698c69ec4245e2194 | |
| author | Jose Antonio Ortega Ruiz <jao@gnu.org> | |
| Fri, 14 Aug 2015 19:44:46 +0000 (14 21:44 +0200) | ||
| committer | Jose Antonio Ortega Ruiz <jao@gnu.org> | |
| Fri, 14 Aug 2015 19:44:46 +0000 (14 21:44 +0200) | ||
| tree | 086b3b0e253195f57c7ebf78ad236c6e579cc735 | treesnapshot (tar.gz zip) |
| parent | bfb4a8fce5828d15641164b475b830031c6d3335 | commitdiff |
Don't try to turn on geiser-mode in non-scheme buffers
xscheme defines its own scheme-interaction-mode that, quite rudely if
you ask me, calls not only its hooks, but also scheme-mode's. Among
them, turn-on-geiser-mode, causing havoc to users of xscheme's
run-scheme function.
We, ahem, fix this problem by checking that we're actually in
scheme-mode when our hook is called.
Thanks to Federico Beffa for his reports.
xscheme defines its own scheme-interaction-mode that, quite rudely if
you ask me, calls not only its hooks, but also scheme-mode's. Among
them, turn-on-geiser-mode, causing havoc to users of xscheme's
run-scheme function.
We, ahem, fix this problem by checking that we're actually in
scheme-mode when our hook is called.
Thanks to Federico Beffa for his reports.
| elisp/geiser-mode.el | diffblobblamehistory |