Helix editor keybindings

[Alcampopiano]

Hello,

I use the helix editor. I see marimo has vim key bindings but not helix keybindings. There was a note here that made me think marimo might support helix but it does not currently. Jupytext is interesting as you can use any editor, but not nearly as nice imo as having code+output+kernel all in one place like marimo.

For a bit more context, I use notebooks in the following ways:

1. Validation interface (e.g., develop a dbt model in helix, validate the build in a notebook, look at visuals, etc).
2. Machine learning prototyping
3. Library development where the notebook is the interface for me to test the lib that I am working on (a "run" interface, etc).

It's all connected and LLMs are used throughout, usually all embedded with my text editor in a CMUX session.

It would be great to have the same text editing experience in marimo when I switch over to the notebook in my workflow. So, the whole workflow is terminal centered, driven where needed with LLMs, and jumping to text editing to the notebook feels seamless in terms of muscle memory.

Thanks for marimo!

[dmadisetti]

Hey, unlikely we'll add first class support in the short term- however here's keybinding map to give you helix keys:

# Helix-flavored keymap for marimo
# =================================
#
# Merge the section below into your marimo config:
#   - in pyproject.toml  ->  keep the [tool.marimo.keymap] header (as written)
#   - in marimo.toml     ->  use [keymap] / [keymap.overrides] instead
#
# How this works: marimo has no Helix mode, so this builds on the `vim` preset
# (the @replit/codemirror-vim engine) and remaps the distinctive Helix keys via
# the companion `helix.vimrc` file (loaded by the `vimrc` path below).
#
# LIMITATIONS (because the engine is vim, not Helix):
#   - Helix is selection-first (motion selects, then a verb acts). vim is
#     verb-then-motion. So `w d`, `f x d`, multiple selections, `;`/`,`
#     selection collapse, and `s` (select-in-selection) are NOT replicated.
#   - `d` / `c` / `y` keep vim's verb-then-motion behavior.
# Only the single-key rewrites that vim can express are emulated; see helix.vimrc.

[tool.marimo.keymap]
preset = "vim"          # Helix builds on the vim modal engine
vimrc = "helix.vimrc"   # path (relative to this config file) to the Helix remaps
destructive_delete = true

and the corresponding vimrc

" Helix-flavored remaps for marimo's vim preset.
" Referenced by keymap.toml via `vimrc = "helix.vimrc"`.
" Only single lhs->rhs rewrites are supported by marimo's parser (parseVimrc).

" Helix goto mode (g-prefix)
nnoremap gh 0
nnoremap gl $
nnoremap gs ^
nnoremap ge G
" gg (start of file) and gd (go-to-definition) already ship with the vim preset

" Helix line selection / extend
nnoremap x V
vnoremap x j

" Helix uses U for redo (vim uses Ctrl-r)
nnoremap U <C-r>

" Helix match-bracket lives under m
nnoremap mm %

" insert-mode escape convenience (matches configs/.vimrc precedent)
imap kj <Esc>

---

But you can use helix directly. See --watch https://docs.marimo.io/guides/editor_features/watching/

[Alcampopiano]

Thanks very much for this. Appreciate the workarounds here, sincerely.

Would love to see the full support one day, and/or contribute to it. But this is a good start that I can try out.

Yes, the watch mode is also cool. I usually try not to have code and output in separate places, but suspect that this is a good option for many people. Thank you very much!