summaryrefslogtreecommitdiff
path: root/alacritty_terminal/src/grid/resize.rs
diff options
context:
space:
mode:
authorChristian Duerr <contact@christianduerr.com>2020-07-14 15:17:29 +0000
committerGitHub <noreply@github.com>2020-07-14 15:17:29 +0000
commit183622e9433c25676b2f3a9d8314f1e19089a26c (patch)
treee02abce89f47c1c30d102ee0b1b441c7388030be /alacritty_terminal/src/grid/resize.rs
parent76a4c373da48a4477c07b844442e5599fbd37ada (diff)
downloadalacritty-183622e9433c25676b2f3a9d8314f1e19089a26c.tar.gz
alacritty-183622e9433c25676b2f3a9d8314f1e19089a26c.zip
Fix movement within search matches
Previously the SearchEndNext and SearchEndPrevious match acted exactly like the SearchNext and SearchPrevious action, however this is not how vim works. In vim, regardless of direction the `gN` action always jumps to the next match start to the left of the cursor, while the `gn` action always jumps to the next search end to the right of the cursor. While both approaches might seem reasonable at first, vim's approach has a significant advantage w.r.t. predictability and automation of the movement. By always knowing which direction the motion goes to, this allows for mappings that reliably navigate inside the current match regardless of the global search direction. So deleting until the end of the match would always be `dgn` for example, regardless in which direction the user has jumped to it. Fixes #3953.
Diffstat (limited to 'alacritty_terminal/src/grid/resize.rs')
0 files changed, 0 insertions, 0 deletions