-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
M-backspace does not effectively delete words in ansi-term #8
Comments
Thank you for submitting your fix. Isn't it better if the entire function I think your verification snippet needs to be immediately after I propose you change it as:
What do you think? |
I don't know exactly what the whole mode is doing (I discovered it while trying to understand why M-backspace was not working), but I think it would even make sense to disable the whole mode in |
Yes, you are right, disabling the entire mode inside "term-mode" is best. I added this to my "init.el" to test the idea:
Then starting new Can this be added as part of the setup of spacemacs? I can also add this snippet to the documentation (README) of |
Ah ! I finally found the correct solution ! That's it :) |
I think I understand it now, remap actually causes the command to take over whenever |
I like this idea: I will test that myself now. |
It works. I tested with Now, @wizmer if you submit a pull request with this change I will merge it. Thank you for this very nice solution. |
It has been merged. Melpa will pick it up automatically, let's see how it goes. |
Description
M-backspace visually delete a word in ansi-term but when Enter is pressed the deleted word is still part of the command.
Reproduction guide 🪲
Observed behaviour: 👀 💔
The "ls" command is performed even it had been deleted
Expected behaviour: ❤️ 😄
The "ls" command should not be performed.
The problem is that M-backspace is overriden by clean-aindent-mode and set to (clean-aindent--bsunindent ARG)
Maybe clean-aindent should always be disabled when being in term-mode ?
PS: The issue was originally opened here: syl20bnr/spacemacs#9564
The text was updated successfully, but these errors were encountered: