Skip to content

v0.4.3

Choose a tag to compare

@github-actions github-actions released this 02 Aug 08:17
· 94 commits to main since this release

jupynvim v0.4.3

Your leader keys are your own again.

Keybindings only while connected

jupynvim used to bind <leader>e, <leader>E, <leader>ff, <leader>/, <leader>sg, <leader><space>, <leader>tr and <C-/> at startup, in every buffer of every filetype, whether or not you ever opened a notebook.

They are borrowed only while an SSH session is active now. If you already had a mapping, jupynvim takes the key on connect and restores yours exactly when the session ends. Keys you had not mapped stay bound and fall back to the local equivalent (#24, thanks @SuperCowProducts).

<leader>e and <leader>E differ again

Both had quietly collapsed onto the same call, so the root-dir versus cwd split your distro gives you vanished once jupynvim loaded. <leader>e opens the project root of the remote file you are in, found by walking up for a .git. <leader>E opens the remote working directory, which :JupynvimRemoteCd sets.

Faster remote listings

fs_list called metadata() and symlink_metadata() on every entry, one after the other, and the frontend only ever reads three fields. On a filesystem where metadata is cheap you never noticed; on an NFS home you waited seconds for a directory that a parallel filesystem rendered instantly. It now takes the kind from the dirent and only follows actual symlinks.

The linux binary keeps itself in step

Deploying to a remote always compared your local cross-build against the one on the remote and uploaded on mismatch, but nothing ever rebuilt it. It could sit weeks behind the source while every connect compared it against its own upload and correctly concluded there was nothing to send.

Connecting now rebuilds it locally first when it has fallen behind core/, then uploads. Never on the remote. If you have the cross-build toolchain, a connect after changing the backend will pause to rebuild; if you do not, you get the same message as before telling you what to install.

Neovim deprecations

vim.loop, nvim_buf_set_option, nvim_buf_add_highlight, termopen and vim.tbl_islist are gone, so jupynvim keeps working as Neovim removes them (#26, thanks @navdeeprana).

Full Changelog: v0.4.2...v0.4.3