vscode-jupyter VS Vim

https://github.com/microsoft/vscode/issues/4490

It looks like there are a number of vscode extensions for recording macros:

- https://www.google.com/search?q=vscode+macro+recorder

- https://marketplace.visualstudio.com/search?term=Macro&targe...

- the macro-commander README explains its JSON-based macro language. YAML might be easier to maintain than JSON. https://github.com/jeff-hykin/macro-commander#what-are-some-...

For teams with multiple editors, you can specify workflow automation scripts with shell scripts or ci container/cmd YAML, and/or pre-commit.yml instead of with an IDE-specific tool.

Isn't there native real-time collaboration functionality in vscode/vscodium that would be useful for a native macro recording feature? (Edit) Live Share can't be installed in vscodium. https://github.com/VSCodium/vscodium/issues/128

Support for jupyter-collaboration Y.js CRDT could be added to vscode-jupyter and/or a more generic extension: "Support for real-time collaboration in the extension?" https://github.com/microsoft/vscode-jupyter/discussions/1293...

jupyterlab/jupyter-collaboration:

Check out this GitHub issue. Similar to your needs, the reply said

It looks like this. I resubmitted a new feature request.

I don't like the fact that Visual Studio Code thinks a notebook has changed, while Git knows it isn't. According to issue #9514, this is something that should be fixed in the core of Visual Studio Code. So, I'm not really sure why issue #83232 (or #24883) is closed.

I wish for a simple option in VS Code: On close of a Jupyter Notebook clear its output. Or something that separate the display of the output from the saved file (Still `ipnyb` file). See [1].

[1]: https://github.com/microsoft/vscode-jupyter/issues/9514

jupyter won't work on vs-code

If that doesn't fix it, can you log an issue here? https://github.com/microsoft/vscode-jupyter/issues

I find the Vim extension for VS Code has macro support that is good enough for most of my use cases (if you’re a fan of Vim key bindings - obviously).

https://github.com/VSCodeVim/Vim/blob/master/ROADMAP.md#repe...

that's why I just use https://github.com/VSCodeVim/Vim if I have to use VSCode

They have discussions enabled on the GitHub repository; eventually r/vscode might be of help.

What you would learn from using a neovim addon for VS Code covers most of the first point and some of the second - VSCode Vim lets you run neovim in a headless mode that relays keypresses to it, and emulates several popular addons. It also comes without quite as much hassle as comes from the second step of learning to configure vim/neovim yourself. Most VSCode extensions work pretty well out of the box, maybe requiring you to add the path to a compiler/interpreter that is not on your PATH.

The extension does have visualedit. You can check the list of supported features here: https://github.com/VSCodeVim/Vim/blob/HEAD/ROADMAP.md

I though VSCode's vim emulation had issues with code folding

Either I go with K552 or save for RK84 if not CB-GK-16 and both of these are pretty good choice that's certain, or I go with 617 Fizz and use VIM keybinding which Isn't an issue for me cause I've been using NeoVim for more than 1 year, you can grab my dotfiles if you want. Most people won't go with 60% cause they are used to arrow, home, end ... keys so am I with vs code but today I found out about vscodevim extension which enables vim keybinding , these keybindings pretty easy to use more than arrow, home, end .. keys if yo're a vim user like Shift + $ = end, Shift + 0 = home, in visual mode V to select text etc ...