The terminal is an essential tool,1 but also one whose tasks are most easily automated and optimized.
Most of the time spent on the command line is on non-value-adding tasks, like moving files around, executing programs, installing dependencies, and checking system status.2 These tasks are necessary, but do not end up in your final deliverable, i.e. a publication, code, or other project output.
Therefore, you should aim to spend as little time in the terminal as possible, focusing instead on value-adding tasks like writing programs, analyzing data, making visualizations, etc.
Here are some ways to automate or speed up terminal tasks. I’m assuming you use bash, but the items here are applicable to most terminals.
- Shorten commands using aliases and scripts
- Use reverse-i-search to find past commands
- Check system status using htop
- Split one terminal into several with tmux
- Download files faster using aria2
- Set up key-based authentication for ssh and Github
- Try out other terminals
1. Shorten commands using aliases and scripts
This one seems obvious, but if you run the same set of commands often, turn them into aliases. I use aliases for computers that I ssh into often, e.g.
#!/bin/bash alias hostname="ssh <username>@<hostname>"
Another use case is for aliases is to shorten series of commands, like navigating to a directory and running a script.
#!/bin/bash alias intera="cd ~/catkin_ws && source intera.sh"
If a series of commands is longer or more complicated (e.g. building and running code), it may be better to turn it into a shell script, which will allow you to take advantage of for loops, command line arguments, etc.
2. Use reverse-i-search to find past commands
Related to the first point, avoid typing out commands, especially if you have typed a similar one already. Besides using tab-autocompleting aggressively, I also use reverse-i-search all the time to search my command history. Activate reverse-i-search using
Ctrl+r and then type in a query to find matches. Hit
Ctrl+r again to find the next match.
3. Check system status using htop
htop is an improved version of the
top command, with colors, better navigation, and other features.
Besides checking system usage, I also use this to find (
F4) and kill (
F9) processes as root (
4. Split one terminal into several with tmux
Use tmux to create and switch between multiple terminal panes within one window.
Another benefit to tmux is that these terminals will persist even if your ssh connection drops. Simply run
tmux attach after ssh-ing back in to return to your panes.
5. Download files faster using aria2
aria2 is an alternative to
curl that parallelizes downloads:
$ aria2c -x8 <URL>
-xN specifies how many connections to open for parallelization.
6. Set up key-based authentication for ssh and Github
Instead of typing your password each time you ssh or push/pull from Github, use key-based authentication. It only takes a few minutes and has the dual benefit of being easier and more secure than password authentication.
To set up key-based authentication for ssh, see this DigitalOcean post: How To Set Up SSH Keys. You’ll need to do this once per computer you want to
ssh into. For Github, follow the steps outlined here: Connecting to Github with SSH
7. Try out other terminals
You can also explore beyond bash and try terminals with more features. I use zsh as my default shell with plugins for jumping between directories, better autocomplete, etc. If you’re interested in zsh, check out these articles on how to get started: Articles from the Oh My Zsh wiki.