-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<up> key for terminal history #5
Comments
my here works fine. (I'm using hkbb's I haven't map any other keys with plugin (it's really simple you can check the plugin through check your up mapping with |
I have the same issue on multiple terminals across OS X and Linux, all of which are using default settings. And it only happens when the plugin is enabled. It's not only |
so you met problems on OS X and Linux? You can try uncomment all the mapping / commands in the plugin and see if things are different. https://github.com/gu-fan/simpleterm.vim/blob/master/plugin/simpleterm.vim#L367 |
I commented out the following line, and that fixed it. simpleterm.vim/plugin/simpleterm.vim Lines 388 to 391 in 669d46d
Not sure why--but that is definitely the problem. Feel free to close, since you can't replicate it. I have a Macbook Pro running High Sierra. |
fine |
Thanks. I had to disable this plugin too because arrow navigation was broken. I'm using OS X 10.14.3 with iTerm 3.2.7 and I'm having the issue as well. Arrow keys get messed up. Pushing down arrow pulls me out of terminal insert mode into terminal normal mode. |
^ Noticed same issue on OS X 10.14.4 using iTerm 3.2.1. |
Thank you for the excellent plugin.
However, when typing in the terminal, pressing the
<up>
arrow key does not let me see my last command. Instead, it says:When I disable this plugin, the
<up>
and<down>
keys for scrolling through the history work as normal. Is there a workaround? Notably, thehistory
command still works--so history is being collected, it seems the keymapping is just messed up somehow.The text was updated successfully, but these errors were encountered: