Skip to content

v0.4.0

Choose a tag to compare

@github-actions github-actions released this 15 Jun 17:54
· 129 commits to main since this release

jupynvim v0.4.0

Remote workspace over SSH. nvim and the UI stay local while only the Rust backend runs on the remote, so you can edit files, run Jupyter kernels, browse, search, and open terminals on a remote machine or HPC cluster as if it were local. Built on plain ssh, so it works where SFTP/scp are disabled and inbound ports are firewalled (tested on PSC Bridges-2).

Remote workspace (new)

  • Connect over SSH. :JupynvimConnect <alias|user@host> authenticates once (password, 2FA) and keeps a ControlMaster socket alive across nvim restarts. :JupynvimDisconnect and :JupynvimUseLocal switch back.
  • Any file, not just notebooks. Remote paths use the jupynvim://<alias>/<path> scheme. Open and save any file; .ipynb opens as a notebook with the kernel running on the remote.
  • File browser for the remote tree (:JupynvimExplorer, <leader>e while connected).
  • PTY terminals, VSCode-style. A bottom terminal (<C-/>) and a second one on the right (<leader>tr) tile together, so you can run a job in one and a tool like Claude Code in the other, all on the remote. Resize with Shift+hjkl in normal mode (or Ctrl+arrows, also in insert). Full vi editing on the shell prompt.
  • Live ripgrep search across the remote into the quickfix list (:JupynvimGrep, <leader>/), streamed as matches are found.
  • Slurm. :JupynvimUseJob <alias> [<jobid>] routes the kernel through an srun overlay so it lands on an allocated compute node.
  • Multiple remotes coexist with local; each buffer routes to its own connection.
  • Binary auto-deploy. The Linux backend is cross-built and uploaded to the remote on connect when it is missing or out of date.
  • Per-mode Kitty graphics. Remote image bytes are encoded locally, so plot data never crosses the link more than once.
  • Remote LSP relay (partial). Kernel completion and hover work over SSH; a full editor language-server relay is in progress.

Notebook UI

  • VSCode-style cell layout with uniform frames. Outputs are real buffer regions you move through with full vim motions.
  • Per-cell execution timing badge in the cell footer ([n] ✓ 0.1s), persisted in the notebook so it survives save and reopen. Clearing the output clears it.
  • One-shot cell navigation (animated scroll off in notebooks; set smooth_scroll = true to restore it).
  • Markdown: gx on links, table rendering, fuller inline syntax.
  • Hybrid relative line numbers; statuscolumn selection bar.

Kernels

  • Project-local venv discovery (.venv, venv, env) in the picker, plus remote auto-venv.
  • Lists conda envs without ipykernel and auto-installs ipykernel on first pick.
  • Discovers module-loaded anaconda via PATH and surfaces kernel start errors.

Fixes

  • Cell frames stay aligned and stable across layout changes (terminal split, explorer, picker, notify popups). Root cause was reading the gutter width from a transiently wrong textoff.
  • Kernels are killed on SIGTERM, SIGHUP, and disconnect instead of being orphaned, so ipykernel processes no longer pile up.
  • Execution order of "run all cells above/below" (#15, thanks @idanarye; incorporates #14).
  • Many remote terminal, search, and LSP robustness fixes.

Known issues

  • In placeholder image mode, a Kitty image cell can occasionally fall back to its font glyph (a colored block) after a full redraw on some terminals. The image id is derived from the editor background so leaked cells blend on a dark background, but a cell over a light image area can still show. This is terminal-layer behavior and is not reproducible without a Kitty terminal.
  • The right cell border cannot be drawn on wrapped continuation rows (Neovim has no per-visual-row virtual-text API), so very long lines show a gap on the wrapped portion.

Install

lazy.nvim users get the prebuilt mac-arm64 or linux-x64 binary on update; other platforms build via cargo. See the README for remote setup.