ideavim VS fish-shell

[this neovim plugin](https://github.com/abecodes/tabout.nvim) helps me get out of double quotes and parenthesis while being in insert mode (I use [ideavim](https://github.com/JetBrains/ideavim/)). The present implementation of this behaviour in the IDE as [smart keys](https://www.jetbrains.com/help/idea/settings-smart-keys.html) isn't cutting it for me.

IntelliJ with Vim bindings is really good! It is actively supported so patches come often to fix some discrepancies with the original software. It even supports a handful of plugins out of the box.

" https://github.com/JetBrains/ideavim/wiki/IdeaVim-Plugins set clipboard+=unnamed set clipboard+=ideaput set ideajoin set idearefactormode=keep set incsearch " set relativenumber set showmode set hlsearch set surround set visualbell set commentary set highlightedyank set argtextobj set matchit set multiple-cursors " requires easymotion and ace-jump plugins set easymotion " requires quickscope plugin set quickscope

For partial chest hair, use IdeaVim

The biggest advantage of vim is the movements (key bindings), and there are plugins for many editors for that, e.g. https://github.com/JetBrains/ideavim

There are many apps, web sites, IDE plugins, and extensions that have vim keybindings. You can use vim keybindings all the time, everywhere.

There is a nerdtree plugin for ideavim https://github.com/JetBrains/ideavim/wiki/NERDTree-support

ideavim has vimscript, but I am not sure how "full" it is, never tried.

IntelliJ IDEA makes it definitively easy to start without setting things up. IdeaVim makes it better for a Vim user. But also frustrating, as certain Vim-features don't work.

Reminds of the note at the bottom of Fish's releases. It's there because the build system cannot determine the current version for some reason. Hopefully that will go away now that they have switched to a different language / build system. The custom tarball is used by Arch Linux at the very least.

https://github.com/fish-shell/fish-shell/releases/tag/3.7.1

https://github.com/fish-shell/fish-shell/issues/7772#issueco...

https://gitlab.archlinux.org/archlinux/packaging/packages/fi...

A recent practical example of the former: the fish shell re-wrote incrementally from C++ to Rust, and is almost finished https://github.com/fish-shell/fish-shell/discussions/10123

An example of the latter: c2rust, which is a work in progress but is very impressive https://github.com/immunant/c2rust

It currently translates into unsafe Rust, but the strategy is to separate the "compile C to unsafe Rust" steps and the "compile unsafe Rust to safe Rust" steps. As I see it, as it makes the overall task simpler, allows for more user freedom, and makes the latter potentially useful even for non-transpiled code. https://immunant.com/blog/2023/03/lifting/

And this discussion from November has an update on the progress: https://github.com/fish-shell/fish-shell/discussions/10123

We're using bash as our terminal shell for now (it is standard in many distros) but it is not the only one out there. If you want to test out zsh, fish or oh-my-zsh, you will see that there are a few differences and the features are usually the main differentiator. Try that, poke around.

They have a variety of reasons to move to rust, as outlined in their original rust discussion[1]. Mostly around finding other contributors, and adding an async/parallel mode they're comfortable with.

[1] https://github.com/fish-shell/fish-shell/pull/9512