infopane: DoKeyEvent: it is buggy, let's add a TODO for now
This commit is contained in:
parent
fade304667
commit
8632b82cbe
1 changed files with 14 additions and 0 deletions
|
@ -143,6 +143,20 @@ func (h *InfoPane) DoKeyEvent(e KeyEvent) bool {
|
||||||
}
|
}
|
||||||
|
|
||||||
if !more {
|
if !more {
|
||||||
|
// If no infopane action found, try to find a bufpane action.
|
||||||
|
//
|
||||||
|
// TODO: this is buggy. For example, if the command bar has the following
|
||||||
|
// two bindings:
|
||||||
|
//
|
||||||
|
// "<Ctrl-x><Ctrl-p>": "HistoryUp",
|
||||||
|
// "<Ctrl-x><Ctrl-v>": "Paste",
|
||||||
|
//
|
||||||
|
// the 2nd binding (with a bufpane action) doesn't work, since <Ctrl-x>
|
||||||
|
// has been already consumed by the 1st binding (with an infopane action).
|
||||||
|
//
|
||||||
|
// We should either iterate both InfoBindings and InfoBufBindings keytrees
|
||||||
|
// together, or just use the same keytree for both infopane and bufpane
|
||||||
|
// bindings.
|
||||||
action, more = InfoBufBindings.NextEvent(e, nil)
|
action, more = InfoBufBindings.NextEvent(e, nil)
|
||||||
if action != nil && !more {
|
if action != nil && !more {
|
||||||
action(h.BufPane)
|
action(h.BufPane)
|
||||||
|
|
Loading…
Reference in a new issue