athame VS Vim

What does ngs do regarding text input... using readline like bash does? Or your own implementation? https://github.com/ardagnir/athame sounds so good for my vim-washed computerbrain. I imagine you don't want to embed NeoVim in your interactive shell (or do you????), but I'm wishing of that being provided in my next era dreamed-of shell <3

vi-mode... perhaps https://github.com/ardagnir/athame ?? perhaps embedding neovim??? but at least the basic modal editing that readline provides.

https://github.com/ardagnir/athame is an interesting looking project, I'd love to have that kind of vimability but am far too maxed out with configuring my tooling so I settle for whatever vi plugin came with oh-my-zsh.

None of these are major criticisms. But I'm wondering if others have also experienced them. I'm also wondering if anybody has found something better than your shell's native vim mode. For example, athame, which sounds great but has gotten very dusty in recent years.

Oh, I misunderstood "commandline editor". To compensate, can I offer this: https://github.com/ardagnir/athame

Athame does this with Vim. I've made a couple of attempts at doing the same thing with Neovim but never made it to the point where it became actually usable (there's a number of issues to overcome, e.g. bash statically linking readline so you can't LD_PREALOAD your own readline replacement, neovim not being very happy with single-line UIs...).

Athame patches readline to be vim-y, but that's usually unnecessary since most shells support vi keybindings. This might be better, since it is truly a vim session (and not emulation), but I haven't used it so idk.

You can test too https://github.com/ardagnir/athame

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 ...