3 ms·
Yeah I tried zsh a few times and never really thought it gave me that much relative to my existing bash config. Fish on the other hand has stuck, and I'm still
by mplanchard 3y ago
Yeah I tried zsh a few times and never really thought it gave me that much relative to my existing bash config.
Fish on the other hand has stuck, and I'm still discovering nifty new built in features, like the fact that if you type `kill`, you can tab-complete on process names, so like if I want to kill emacs, I can type `kill ema<tab>` and select from the following:
> kill ema
3296 (.blueman-applet) 3595 (.blueman-tray-w) 9324 (emacsclient) 9327 (emacs) 9557 (emacsql-sqlite)
If there's only one match it completes the PID for you, and of course if you start typing a PID and press tab it shows the process names along with the potential completions.
I use starship for prompt customization, which is nice because my config transfers just fine from bash over to fish.
- wyclif 3y agoWhat I do is use zsh as my default shell and use oh-my-zsh, but keep a very simple config for my ~/.bashrc, something like: [ -f ~/.fzf.bash ] && source ~/.fzf.bash source /Users/wyclif/.config/broot/launcher/bash/br This gives me the best of both worlds.
- JNRowe 3y agoFWIW, that is also the default behaviour of zsh's standard completion subsystem for kill. You can try it yourself: "zsh -f" to get a shell without reading a fancy config, start compinit, "kill <Tab>". You can even disable verbose mode via zstyle, should you be the type of person that likes a simple pid list like bash's completion project provides. To me this level of customization is the main feature zsh provides, but not everyone incessantly turns every knob they see.
- mplanchard 3y agoNice! It's super useful in fish, good to know it's in zsh too