Open BooAA opened 6 years ago
This is expected, we are simply following the usual keymap rules here: [remap eval-last-sexp]
doesn't work since eval-last-sexp
isn't bound anywhere in the keymap at that point, but hydra-vi/eval-last-sexp
is, that's why [remap hydra-vi/eval-last-sexp]
works.
Oh..., sorry for my poor English expression.
I mean that [remap eval-last-sexp]
works but [remap hydra-vi/eval-last-sexp]
doesn't work, which confusing me.
[remap hydra-vi/eval-last-sexp]
doesn't split window and eval the expression, which is very strange.
Generally, I have "E" bind to eval-last-sexp so that I can quickly eval elisp code.
But when editing scheme code, I want "E" to be remapped by another function customized for scheme-mode. Here's how I do it.
And that I saw this post #175 , so I think I must remap hydra-vi/eval-last-sexp
but not
However , the weird thing is that the first one doesn't work but the second one does.
The first one didn't split the window and only open the REPL without eval my code. And I was in the buffer with REPL opening.
The second one splits window and eval the code. And I was stayed at the origin buffer.
The reason I know whether the code is evaluated is by making the expression before cursor with some bugs and the first one doesn't report but the second one does.
I haved tried directly M-x and call BooAA/scheme-send-last-sexp , the result is correct. So I think my customized function should work independently.
I doubt that the last line of BooAA/scheme-send-last-sexp (e.g. scheme-send-last-sexp) was not evaluated, and maybe the function stuck after running BooAA/get-scheme-proc-create so that it doesn't split window nor eval scheme code as well.