VSCodeVim/Vim

`j` and `k` do not account for tab size

Open

#2,458 创建于 2018年3月20日

在 GitHub 查看
 (10 评论) (21 反应) (1 负责人)TypeScript (12,664 star) (1,271 fork)batch import
area/motionhelp wantedkind/bug

描述

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG What happened: Note: The second line start with a tab indent. Default(disabled vim plugin): foo enable vim plugin:(pressing gj can solve, but what about insert and visual mode) foo2 or Insert mode: foo3 Visual mode: bar2

What did you expect to happen: Like vscode default show or native vim. How to reproduce it (as minimally and precisely as possible):

Environment:

  • Extension (VsCodeVim) version:0.11.2
  • VSCode version:1.12.1
  • OS version:4.15.9-1-ARCH

贡献者指南

技术栈
typescript
领域
tooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
TypeScriptVim motions knowledge
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Investigate the code handling `j` and `k` movements in the VSCodeVim extension. Look at the cursor move functions, particularly how they handle screen lines versus logical lines, and how tab size is accounted for. Check if tab size is used elsewhere, e.g., in the `gj` and `gk` implementations. Also review the test cases for motions to ensure new behavior is tested. Consider both normal, insert, and visual modes.