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.

1 files changed, 2 insertions, 2 deletions

diff --git a/alacritty.yml b/alacritty.yml
index 5a14a417..63d8f6c7 100644
--- a/alacritty.yml
+++ b/alacritty.yml
@@ -534,8 +534,8 @@
 #   - ToggleSemanticSelection
 #   - SearchNext
 #   - SearchPrevious
-#   - SearchEndNext
-#   - SearchEndPrevious
+#   - SearchStart
+#   - SearchEnd
 #
 #   (macOS only):
 #   - ToggleSimpleFullscreen: Enters fullscreen without occupying another space