resh
resh copied to clipboard
-bash: bash_execute_unix_command: cannot find keymap for command
struggling to find out this one,
ctrl-r, works fine for a while, and then at some point it starts throwing errors until I close the bash shell and start a new one.
-bash: bash_execute_unix_command: cannot find keymap for command
running the latest, and a dig through the issues doesn't give me any clues,
○ → reshctl update
Please report any issues you encounter to: https://github.com/curusarn/resh/issues
Looking for the latest release ...
* Latest version: 2.7.13 (git tag: v2.7.13)
* Resh is up to date - nothing to do - exiting.
any idea of what could be?
Hey, I haven't seen this error yet.
What OS are you on? What version of bash are you running?
I'm seeing this issue as well. I'm using the latest version of reshctl (2.8.1). Here the other versions you asked for above:
- OS: Ubuntu 21.10
- bash: 5.1.8(1)-release (x86_64-pc-linux-gnu)
Is there anything that I can provide to help debugging / fixing this issue?
sorry didn't see the issue update,
bash --version GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
I can confirm this error. Clean install of Ubuntu 22.04 and resh was the first application installed. My uncomfirmed feeling: last command before crash contains tilde ~ (i.e cd ~/abc/abc/abc ) I am dedicated to my bash history and now I have to search for different software... I am ready help to debug it.
I can confirm this on fresh Ubuntu 22.04.1. It seems to happen randomly for me, not related to commands with ~
, didn't use such today and got to this state several times already. I will observe more if specific commands or actions affect this or not.
Usually, it is enough to disable and reenable binding with reshctl disable ctrl_r_binding
and reshctl enable ctrl_r_binding
, then it works again for some time after that.
The same is happening to me. Linux Mint 21.1 Cinammon.
This bug still persists in version 3.0.1. And because apparently the command enable ctrl_r_binding
are not available anymore, the only way to remedy this is to reopen the console.
Update with some more information: GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu) Kernel: 5.15.0-71-generic #78-Ubuntu SMP Tue Apr 18 09:00:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Unfortunately, this bug started to repeat more frequently after the latest release and I will have to stop using it but I hope it gets fixed soon. It is a great tool.
I just (finally) upgraded my work machine from Ubuntu 18.04 to 22.04 and I'm seeing this frequently now.