You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. :ConqueTermSplit bash
2. Attempt <esc>k for previous command within bash shell. (or any <esc>
command)
What is the expected output? What do you see instead?
Expect bash history navigation, but <esc> leaves vims insert mode (as
expected, but unwanted in this context.)
What version of the product are you using? On what operating system?
Vim 7.2
Conque plugin 1.0
Debian sarge, rxvt-unicode
Please provide any additional information below.
Requesting a vim-modeline invocation mode (:ConqueTermVimModeline bash)?
to support sending <esc> to shell.
Original issue reported on code.google.com by anony...@gmail.com on 11 Apr 2010 at 11:24
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. I find this irritating as well.
What I hope to do in the next version is add a configuration variable for
people to
choose a custom key to leave insert mode. So if a user chooses say <Ctrl-space>
then
pressing <Esc> would just be sent to the terminal, and stuff like vim modeline
and
the alt key would work normally.
Original comment by nicora...@gmail.com on 12 Apr 2010 at 2:02
Fix released with 1.1
From manual:
Normal mode key
let g:ConqueTerm_EscKey = '<Esc>'
This option lets you choose which key you will use to leave insert mode, which
also
takes you out of the terminal input mode. By default this is the <Esc> key,
like a
normal Vim buffer.
However, you may want to be able to send the <Esc> key to the terminal, instead
of
leaving insert mode, for example if you use Vim key mappings to edit the bash
command
line. In this case you can configure Conque to use a different key to leave
insert
mode, and pressing <Esc> will send that key press to the terminal.
Control keys are the only that consistently work. Many others, e.g. the <F->
keys,
are internally coded with an escape at the beginning, and therefore won't work.
A
control key such as <C-x> will work fine.
Original comment by nicora...@gmail.com on 28 May 2010 at 5:57
Original issue reported on code.google.com by
anony...@gmail.com
on 11 Apr 2010 at 11:24The text was updated successfully, but these errors were encountered: