Suggested bash doc improvements

Site Feedback
1

I just started using Atuin. It’s awesome! Thanks for making it.

I use bash and was initially confused as to why the recommended installation method installs bash-preexec while elsewhere it’s stated that Atuin works better with blesh. I also didn’t realize that my bashrc would be automatically updated and that both tools have specific guidelines on where to import them in bashrc.

Once I got it working I combined my understanding with some of the ideas from this discussion Atuin, bash, and ble.sh to make some suggested doc improvements. I think they would improve the first install experience for new bash users that, like me, aren’t super familiar with shell behavior but really want what Atuin has to offer!

I made a PR against my fork for now (update bash docs by sociotechnodev · Pull Request #1 · sociotechnodev/atuinshdocs · GitHub). No worries if you don’t want to incorporate them. If you do I’m happy to make an issue, PR to the upstream and tidy up the wording and styling (or let a maintainer do it if that’s the preference).

I also had to add an entry to my vs code keybindings. Just mentioning in case someone comes across this in the future.

    // ctrl+j conflicts with the default blesh configuration
    // this disables the keybinding in vs code
    {
        "key": "ctrl+j",
        "command": "-workbench.action.togglePanel"
    },
2

After reading The new .atuin directory - #9 by AtomicRobotMan0101 I realized I may not be the target audience for the auto install script as I use the dotfile manager chezmoi (I definitely missed the script’s standard output because of this). I still think it’d be beneficial to call out/clarify the bash nuances but regardless I’m a happy user, only sharing in case it’s helpful. I appreciate that Atuin supports bash in the first place despite it’s shortcomings. :turtle: