Skip to content

Helix Mode: vim::NextWordEnd while in helix select mode is one character short #43209

@jrobsonchase

Description

@jrobsonchase

Summary

There seems to be an off-by-one error with the vim::NextWordEnd motion in helix select mode.

Description

Steps to reproduce:

  1. Turn on helix mode
  2. Open a file
  3. v to enter select mode
  4. e to move to and select to the end of the next word.

Expected Behavior:
Cursor ends over the last character in the next word, which is included in the selection.

Actual Behavior:

Cursor and selection end up on the second-to-last-character.

This seems to only affect NextWordEnd. NextWordStart behaves normally both in and out of select mode. NextWordEnd also works fine in normal mode, it's only in select mode that there's a problem.

No config outside of turning on helix mode, no keymap changes.

Zed Version and System Specs

Zed: v0.213.3 (Zed)
OS: Linux X11 ubuntu 24.04
Memory: 62.3 GiB
Architecture: x86_64
GPU: Intel(R) Graphics (MTL) || Intel open-source Mesa driver || Mesa 25.0.7-0ubuntu0.24.04.2

If applicable, attach your Zed.log file to this issue.

Zed.log

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:parity/helixFeedback for Helix parity features

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions