summaryrefslogtreecommitdiff
path: root/src/pattern_test.go
diff options
context:
space:
mode:
authorWilliam Chargin <wchargin@gmail.com>2016-04-12 17:20:30 -0400
committerWilliam Chargin <wchargin@gmail.com>2016-04-14 13:19:05 -0400
commit0c8de1ca4468842429e7cb14ecb79391d896e0e5 (patch)
tree8fb2e9dfe53dd9ea59b6c97492e1380a475a27f0 /src/pattern_test.go
parent935e986be5fe3d6c9ca6fa578d836500a3b31525 (diff)
downloadfzf-0c8de1ca4468842429e7cb14ecb79391d896e0e5.tar.gz
Fix Bash+vimode pre-launch delay
Summary: Fix adapted from [@adamheins: fzf, vi-mode, and fixing delays][1]. [1]: https://adamheins.com/blog/fzf-vi-mode-and-fixing-delays The basic problem is that fzf presses <Esc> to enter vi-movement-mode (as opposed to insert mode) and then presses a bunch of keys to set up the buffer. But the <Esc> keypress is also the prefix for a bunch of other commands, so Bash will dutifully wait an excruciating half-second before actually executing this command. Instead, we bind <C-x><C-a>, which is unused by default and seems reasonably unlikely to be custom-bound, to be another way to enter vi-movement-mode; this binding is unambiguous, so fzf can use it without delay. This change was made by just `:s/\\e/\\C-x\\C-a/gc` in the relevant section, after adding the actual binding and comment at the top.
Diffstat (limited to 'src/pattern_test.go')
0 files changed, 0 insertions, 0 deletions