#Atuin update: I've come to rely on it. It's a must have for my daily shell usage. Works great everywhere ... except on #GitBashForWindows. Lots of problems there. Here's how I solved them:

* Install `ble.sh`. Use `curl` to do this. Do not get it with Git. Do not attempt to build from source.
* Install by sourcing `ble.sh` at the **end** of your `.bashrc`. That's how the instructions about getting it with `curl` tell you to do it. The Git based instructions want you to say something different in your `.bashrc`. You want the `curl` instructions.
* In my install, #Ble was too slow out-of-the-box. Missed keystrokes, etc. I copied the `blerc.template` from the GitHub repo to a local `~/.blerc`, and edited it to disable almost every kind of completion and also syntax highlighting. Speed is now acceptable. (Might be that my #Windows box is too slow. That seems unlikely.)
* I use `vi` mode; #Vim. `ble.sh` picks that up from my `.inputrc`; #Readline. I use #Starship for my prompt. I had to disable in `.blerc` the showing of my current `vi` state (insert, visual, command, etc) and also edit `.inputrc` to not add characters to the prompt to show insert vs command mode. Those changes let me have my normal `starship` prompt.

I do have one problem remaining. It's not related to `atuin`; it's related to the command line itself. In #Bash and #Zsh, it's easy for me to be on the command line and get what I've typed so far directly into my editor; #HelixEditor. Usually something like Esc-v or the like. `ble.sh` doesn't seem to have a way to do that, but maybe I just haven't found it yet.

I've already said I'm becoming a huge fan of #Atuin. I have been an extremely happy user of #fc for years. The great thing about fc is going so quickly from knowing what you want to executing that new command. Atuin doesn't have a fast-path for this. Instead, you (only because you want to edit it) put the command back onto the command line instead of directly executing it. Then you do whatever you normally do on the command line and execute the result.

What I normally do on the command line is (since I'm in Vim mode): Escape (so now I'm in normal mode) v (I'm using #Zsh usually, so that puts me in visual mode) v (and that launches $EDITOR). Then the usual fc-like thing happens.

I want this in atuin. Atuin is written in #RustLang, is #OpenSource, lives on #GitHub, and accepts PRs. So I read the code of conduct, the contributors guide, and talked about it on their Discord discussion. Took me about 40 minutes to write it. It passes all the existing code tests, it passes all the GitHub checks. I'll be using it myself no matter what happens next. I hope it's accepted because I think other people would like it as well.

It's my first contribution to anything in Rust. I look forward to reviews (if it turns out to be interesting to them). I'd love to improve it.

Here's the PR: https://github.com/atuinsh/atuin/pull/2851

Bisher hab ich ja ausschließlich die #Bash verwendet, in Kombination mit #Atuin für eine deutlich bessere History. Farblich angepasst mittels der "PS"-Variable in der Konfigurationsdatei.

Die letzten Tage hab ich ein bisschen umher probiert mit #Fish und #zsh Fish hat mir zu viele komische Eigenheiten. Die Doku ist gut, aber unübersichtlich und dieses doofe gekürze bei den Pfaden war richtig doof. Das kann man abschalten, ja, aber als Standard fand ich es doof. Das PPA für die aktuelle Version im Ubuntu Testcontainer konnte ich nicht hinzufügen. Vielleicht lags auch mal wieder an Launchpad.
Oh-my-fish wird nicht mehr gepflegt, da fehlt ein Maintainer. Weitergehende Anpassungen sollen über eine Webkonsole möglich sein, die lauscht aber nur auf localhost, bringt mir also nix. Andernfalls viel lesen in der Dokumentation.

Es ist also die Z-Shell geworden in Kombination mit Oh-my-zsh und Atuin. Funktioniert richtig super, Anpassungen können mittels "omz" Kommando sehr einfach gemacht werden, sonst ist da auch die manuelle Bearbeitung in der Zshrc ebenfalls sehr einfach möglich wie bei der Bashrc.

Was mich ein bisschen störte war, das viele Themes eine Git-Integration haben und komisch darstellen. Mit dem Theme Fino bin ich zufrieden, was das angeht, da diese den Branch abgetrennt angibt und nicht direkt hinter dem Pfad. 2 Plugins musste ich ebenfalls selbst nachinstallieren (zsh-autosuggestions zsh-syntax-highlighting), wäre super, wenn die ebenfalls in OMZ dabei wären.

Für alle, die die Bash ein bisschen pimpen wollen gibt es da noch "oh-my-bash" 

#Atuin is working great for me (especially with a few configuration tweaks) everywhere and in every #Shell except in complex commands (i.e., commands with pipes and or sub-shells) in Git Bash for Windows #GitBashForWindows. My problem here probably has something to do with the Bash preexec hook or whatever it's called; and it might be fixable.

Here are my tweaks:

```toml
store_failed = true
invert = true # I think this value is a change from the default
search_mode_shell_up_key_binding = "prefix"
```