I thought the default interactive shell is still bash on Ubuntu, dash is only used for /bin/sh, isn’t it? At least bash is also installed by default, as there are so many scripts that wouldn’t run otherwise

I switched to zsh at a time where completion for commands parameters except file paths in bash wasn’t really a thing, you could add some with a script, but they didn’t work well. I’m sure the situation has improved by now, but someone told me recently, there are still no descriptions for the completions. I find it very helpful and it saves me opening a man page a lot of times. For example, typing grep -<Tab> gives me this:

And now I’m so used to many little features (mostly around the syntax) that wouldn’t be a reason to switch on their own, that I find bash cumbersome to use.

Isn’t sha512sum a regular binary, that should not depend on the shell at all? What does nushell do that something like that can break o.O

I used fzf before atuin, and it works pretty similar, but atuin has a few additional features, as it tracks more information than the normal shell history. For example, you can also search only for commands that you executed in the current directory (great for stuff that is project specific). Or, if you use the history syncing feature, you can toggle search for commands you executed on either any or only the current machine.

In zsh, you can configure the completion to also show descriptions.

Thank you, from a quick glance it seems to be able to do everything I need. I will try it for my next load test.

The only thing I still use Postman for at work is when running API performance benchmarks, as I wasn’t yet motivated enough to write a curl wrapper to do such tests and plot the results. Especially when doing things like ramp up etc. it becomes more than a simple for-loop.

Can someone recommend an existing command line tool for that?

Also, even zsh scripts don’t read your .zshrc by default.

Do most packages usually have a manual entry ?

Usually there are manual pages for commands, for libraries and drivers like libwacom it is less common, and they are not necessarily the same as the package name. Some packages also just have a Readme file or an HTML manual installed under /usr/share/doc or similar.

When unsure, I often just check the list of files that belong to a package, most package managers can do it. E.g. on Debian-based (i.e. apt using) distros, dpkg -L $packagename will list it, in arch based distros it is pacman -Ql $packagename.