diff options
| author | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2015-08-14 21:44:46 +0200 |
|---|---|---|
| committer | Jose Antonio Ortega Ruiz <jao@gnu.org> | 2015-08-14 21:44:46 +0200 |
| commit | c71691ab5108aa84162ccae18a354527a6064dd4 (patch) | |
| tree | 3d4b0e57fe2d64a44c5dcb6becf3bdc13b70df36 /doc/img/mod-completion.png | |
| parent | 8ebeaeefbc7850dc19f651a7f5864c207de2ec52 (diff) | |
| download | geiser-c71691ab5108aa84162ccae18a354527a6064dd4.tar.gz geiser-c71691ab5108aa84162ccae18a354527a6064dd4.tar.bz2 | |
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.
Diffstat (limited to 'doc/img/mod-completion.png')
0 files changed, 0 insertions, 0 deletions