Open In: Neovim and Neovide

[wSedlacek]

Summary

This discussion asks for a direction decision. Should Open In grow Neovim and Neovide targets so a file or project opens in those editors the same way it opens in VS Code / Cursor today?

This is a small Open In addition, not in-app vim (#35228). #30660 was a prior attempt.

Why Neovim / Neovide in Open In

A large share of T3 users live in Neovim. Open In already abstracts “open this path in the user’s editor” with the right cwd (and remote host when applicable). Shipping Neovim and Neovide closes an obvious gap without a new product surface.

Neovide fits the existing detected-GUI-editor path. Terminal Neovim wants a path that opens in the thread’s built-in terminal (optional line/column) using the server/environment cwd — otherwise remote projects open the wrong tree.

Proposal

• Add Neovide as a detected GUI Open In target.
• Add Neovim as a terminal-editor Open In target (thread terminal, cwd/line/column aware).
• Keep launches on the server/environment (and remote host when applicable), same as other Open In targets.
• Do not block on in-app vim mode (Opt-in vim keys for editing and moving around the web/desktop app #35228).

Reference implementation

#30660 added Neovim/Neovide Open In targets. Linked as evidence only.

Question for maintainers

Yes, no, or not now: Neovim and Neovide as Open In targets.

[wSedlacek]

Note

🤖 Composer responding on behalf of wSedlacek

Prior effort: #30660.

What we learned trying it

• Neovide fits the existing “detected GUI editor” path; Neovim wants a terminal editor path that opens in the thread’s built-in terminal with optional line/column.
• Launches should use the server/environment cwd (and remote host when applicable), same as other Open In targets — otherwise remote projects open the wrong tree.
• This stays a small Open In addition; it should not wait on in-app vim mode (Opt-in vim keys for editing and moving around the web/desktop app #35228).

[alanjds]

Why is the editor choice a hardcoded list? I mean, we can make it very long and will not be enough.

What about have the "Open In" configurable by the user? The $EDITOR envvar can be a "default system editor", and everything else should be configurable. Not directly asking for a Web UI config, but at least for a way to edit a configuration file to have my custom editor set up!

Does it makes sense?

I mean, I use neovim, but also use code-server, and used openvscode-server in the past. I do not think that it all should be supported and hardcoded in T3.