McFly for better ”ctrl+c”. It also keeps track of what commands you ran in what directory.

https://github.com/cantino/mcfly

.zsh aliases to bash functions.

Thanks for the list though, gonna take a look at a few!

I like bash scripts + auto key! Custom commands with custom keybinds.

aliases in .bashrc

I’d say aliases and functions are your friends here.

I use this method from Luke smith for bookmarking.

https://vid.puffyan.us/watch?v=d_11QaTlf1I

I just have another file for commands.

You can use rofi/dmenu/bemenu. I use kickoff though.

Fish (or zsh with some addons) will give you tab completion based on previous commands, might be something of interest?

Here’s some addon tips if you’d rather run zsh instead of fish:

https://gist.github.com/abhigenie92/a907cdf8a474aa6b569ebe89aeee560d

Fish and its search functionality work great for me.

Obvious things I don’t see mentioned:

• Bash scripts kept in the home directory or another place that’s logical for them specifically.
• history | grep whatever (or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE and HISTFILESIZE environment variables in your system.

I use vi as the command line editor, so fetching history commands is quick:

ESC /searchstring

But if it’s something really frequent or may benefit from parameters, I usually throw a perl or bash script in /usr/local/bin.

Try fzf. The default hooks will launch fuzzy finders for

• C-r: history search
• Alt-c: change directory
• C-t: fill in argument for a nested path

All seem pretty good for your use case.

If you use fish you can use abbreviations

I wouldn’t install a program for this if your use case is simple. You will end up relying on it when there are already some built in tools that can get you 99% of the way there.

1. Bash scripts placed in ~/bin or ~/.local/bin

• Can have simple or complex scripts setup to do whatever you want
• Easily called from terminal or automated through cron or systemd

2. Environment variables set in -/.bashrc

• Great for storing common paths, strings, etc.
• Can be easily incorporated into bash scripts

3. Aliases set in ~/.bashrc

• Ideal (IMO) for common commands with preferred options
• for example you could setup your most used rsync command to an alias: alias rsync-cust=“rsync -avuP”

Edit: rephrased to not discount the tools shared. I am sure if you had a specific reason to use them they could be helpful. But I think for many users the above options are more than enough and are supported pretty universally.

Fish shell. Out of the box it autocompletes taking into account in which directory you are. It’s like bash Ctrl+r but without actually invoking it before. Really ergonomic.

I have a file in my ~ called .alias and it is sourced by any shell I might use (currently just zsh) in it are common aliases like s => sudo and “sudo” => "sudo " (just put this as an alias if you use them a lot, you’ll thank me when you’re trying to use them with sudo)