Using j/k as next/prev conflicts with navigation bindings
vekkt0r opened this issue · 2 comments
It would be nice if the default jk navigation was disabled when in copycat mode (at least when they are used as next / prev binding)
As it is right now tmux first jumps up / down and then to the next copycat item
Hey,
I'm not sure I understand the issue here. Are you using j and k as keys to jump to next, previous copycat item?
Yes sorry, correct.
Maybe i should have phrased this issue a bit differently. What I'm really
trying to do is to have j and k as next, previous keys in copycat mode,
without having to disable the normal j/k navigation in escape mode (because
copycat seems to act on top of escape mode?).
What I would like is for the copycat key bindings to take precedence over
normal key bindings, not in addition to the normal bindning. Would this be
possible?
On Friday, September 4, 2015, Bruno Sutic notifications@github.com wrote:
Hey,
I'm not sure I understand the issue here. Are you using j and k as keys
to jump to next, previous copycat item?—
Reply to this email directly or view it on GitHub
#83 (comment)
.