atuin VS z

I've heard good things about atuin

https://github.com/atuinsh/atuin

The shell history autocomplete seems to be better than the one that comes with Oh My Zsh.

Atuin is lovely, although I found some of its defaults pretty annoying until I changed them:

- It turns out I basically never want fuzzy search through my command history, and certainly not by default. I gave it a try for a couple weeks but it was very frustrating to be searching for a particular command, type in the exact prefix, and have the thing I was looking for hidden among hundreds of irrelevant entries. Solution: search_mode = "fulltext" in Atuin's config.toml

- Having a full screen pop-up appear whenever I hit up was really jarring, especially since I have a habit of hitting up a few times when I'm at the command line thinking of what I need to do next, to sort of refresh my memory on what I was just doing; the popup very effectively destroyed that chain of thought. Solution: eval "$(atuin init bash --disable-up-arrow)" in .bashrc

These are pretty minor issues and it's possible my preferences are just different from most!

Atuin now works really nicely for me. My only outstanding issues are:

- Under mosh the UI ends up corrupting the screen; apparently this is really more of a mosh bug (no alternate screen support) and you can work around it by having tmux/screen running: https://github.com/atuinsh/atuin/issues/1324

- I still don't have a great model in my head of how sync works and find myself occasionally force-syncing across a few systems until I convince myself everything is in the same state.

- It would be nice to have some kind of settings sync so I don't have to make the config changes mentioned above on 10 different systems. Surprisingly I don't see a feature request for this yet so maybe I'll go open one...

Anyway I don't want these issues to stop people from trying Atuin – it's a really nice piece of software. I almost never make changes to the default environment so I consider it a testament to how useful it is that I've added it to all the systems I use regularly!

They recently added sqlite backed history. You can also use atuin[1] for more advanced usecases.

[1]: https://github.com/atuinsh/atuin

I was studying the Atuin crate, and I noticed the following pattern:

You might be interested in https://github.com/ellie/atuin

> Atuin replaces your existing shell history with a SQLite database, and records additional context for your commands.

- Visidata

- z (https://github.com/rupa/z)

- fzf

- vim

- Fastmail

- WireGuard

- draw.io

- PowerShell (it’s difficult to overstate how much PS has improved Windows system administration)

- Microsoft PowerToys

- WSL (alternating joy and extreme frustration)

- Home Assistant

- Airfoil

For even more power use z

https://github.com/rupa/z

- quickly jump to recent directory: https://github.com/rupa/z - however I find it kinda annoying it seems to forget/ignore(?) directories, anyone know of a better version of this?

- quickly opening my personal wiki: https://github.com/francium/dotfiles/blob/master/bin/.local/...

- re-run a script when a file changes: https://github.com/francium/dotfiles/blob/master/bin/.local/...

For `while-watchdo` you, you run it like `while-watchdo "echo hi"`, then in my editor, I have a custom shortcut that does `touch .watchfile` causing the command, in this case `echo hi` to run. I prefer this to tools that retrigger commands as soon as you save _any_ file. Also works in docker containers, edit a file on host, command runs in a container.

2) Well friend, this is where you can have the best of both of worlds. You can just open the file explorer via the CLI. Typically you'll have the xdg-open command that opens the directory in your default file browser. I have that aliased to xdgo. So you can navigate quickly to where you need to be, and then open it visually with xdgo . . There's also other really convenient navigation tools like z (https://github.com/rupa/z) that I can't imagine going without anymore.

I would like to know how you use the terminal and nvim in your daily workflow. Here is mine: I have a shortcut (with raycast) to open alacritty full screen from anywhere. I open alacritty and start the tmux (create work and personal sessions). Then using z navigate to the desired project. Next, I have a bash script pde that opens nvim, and 2 terminal splits below. Nvim opens with alpha-nvim (startify theme). For file explorer I use lir.nvim. Fuzzy finding using fzf-lua. I have harpoon but don't use it very often, instead, I manage buffers with fzf-lua and vim-bbye. When working on multiple files I usually have 2-4 vsplits. I do git stuff mostly using vim-fugitive (gv.vim, resetting hunks with gitsigns.nvim), occasionally git commands from another tmux window. I use auto-save.nvim. My most used command is :F (lsp.bug.format). For movements I use Ctrl+D/U/O/I/, sometimes relative line jumping. Other often movements [q,]q (quickfix jumps), [d,]d (diagnostics jumps), [c,]c (Gitsigns hunks). Alacritty + Neovim view

For general filesystem navigation in my terminal, I'm using z command. But for finer control, I am using the following commands.

z

Do you know about the program z? https://github.com/rupa/z

https://github.com/rupa/z is an awesome command to teleport to your most used directories. It's really handy to jump from a project to another.