From ca0b1fe1a590aa640fb20fcdfde3aeed3a0eac03 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc=20Andr=C3=A9=20Tanner?= Date: Tue, 4 Apr 2017 09:22:26 +0200 Subject: vis: add motions to move by codepoints Some people might prefer this for behavior. Except for that and debugging purposes using `ga` and `g8` it is not yet that useful. --- vis-motions.c | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'vis-motions.c') diff --git a/vis-motions.c b/vis-motions.c index 1ceb958..0166117 100644 --- a/vis-motions.c +++ b/vis-motions.c @@ -491,6 +491,14 @@ const Movement vis_motions[] = { .txt = text_line_char_next, .type = CHARWISE, }, + [VIS_MOVE_CODEPOINT_PREV] = { + .txt = text_codepoint_prev, + .type = CHARWISE, + }, + [VIS_MOVE_CODEPOINT_NEXT] = { + .txt = text_codepoint_next, + .type = CHARWISE, + }, [VIS_MOVE_WORD_NEXT] = { .vis = word_next, .type = CHARWISE|IDEMPOTENT, -- cgit v1.2.3