not really known
Go to file
2024-01-13 18:13:14 +00:00
.vscode first updates 2023-10-29 17:34:56 +00:00
docs/img change images because VSCode moans on publish 2023-12-01 20:01:04 +00:00
res replace simplevim name 2022-11-11 09:47:54 +09:00
src Improve match mode with counts 2024-01-13 18:13:14 +00:00
.eslintrc.cjs format with prettier 2022-11-09 14:35:37 +09:00
.gitignore format with prettier 2022-11-09 14:35:37 +09:00
.npmrc add updated build pipeline template 2022-11-09 13:54:20 +09:00
.prettierrc g commands are implemented 2023-11-12 19:24:48 +00:00
.tool-versions initial commit 2022-11-09 13:28:36 +09:00
.vscodeignore try helix name 2023-12-01 20:05:15 +00:00
build.mjs update build script to only output status in watch mode 2023-12-13 23:29:47 +00:00
index.d.ts add updated build pipeline template 2022-11-09 13:54:20 +09:00
LICENSE.txt initial commit 2022-11-09 13:28:36 +09:00
package-lock.json v0.4.1 2024-01-08 22:33:07 +00:00
package.json repeatLastMotion 2024-01-12 18:53:45 +00:00
README.md more visual mode support 2024-01-08 19:46:25 +00:00
tsconfig.json first updates 2023-10-29 17:34:56 +00:00
tsup.config.ts add updated build pipeline template 2022-11-09 13:54:20 +09:00

Helix for VS Code

   

This is a fork of an older Helix extension which in itself was a fork of the VSCode Vim extension. So there are still a lot of references to Vim in this source code. It is a work in progress.

Commands

The main commands should work but selections currently do not.

Right now commands are hardcoded to the default keymap, hopefully this can be adjusted to the user's keymap in the future.

If something doesn't work, please open an issue.

Performance

For added performance, you can try adding the following setting, and reload/restart VSCode:

"extensions.experimental.affinity": {
  "jasew.vscode-helix-emulation": 1
}

Differences

Window Mode

Due to VS Code having tabs I've needed to add some new windows modes on top of the current Helix ones, these commands are based around movements, (i.e moving the editor from one window to another).

Command Description
ctrl + w, m, v Move editor to the next group vertically (to the right)
ctrl + w, m, s Move editor to the next group horizontally (below)
ctrl + w, m, p Move editor back to the previous group
ctrl + w, m, w Move editor out into a new window (experimental)
ctrl + w, m, j Rejoin editor with main window (experimental)
ctrl + w, c Close window (alias to ctrl + w, q)

Most of the differences will be related to the fact VSCode doesn't have TreeSitter or have access to an AST. So we often need to find other ways of achieving the same action.

  • mif/maf both do the same, they will select the outer function range. Getting the inner function body isn't achievable because LSP doesn't give us that, and we can't hardcode blocks (incompatibilty with python for example)

Movements

Command Description
alt + k Move lines or selection up
alt + j Move lines or selection down
alt + d Add selection to next match (same as ctrl+d)
alt + m Move selection to next match (same as ctrl+k)

Outstanding

Feel free to pick up any of these if you wanted to contribute.

  • #3 Commit checkpoints, extensions don't have access to VS Code's back/forward stack. So it would need to have its own stack in memory which can be manipulated.
  • #4 Custom keymaps, currently keymaps are matching Helix