Long commands can be annoying. It's easy to forget the full directory path to desired commands. It's easy to forget which switches you used, and the sequence of switches and other arguments you need to use.
I address this annoyance in three ways. First, I show how you can
use the history of previous commands to help you run a long command.
Second, I show you how you can add a directory to your
PATH, which can minimize the length of more
common commands. Finally, I show you how you can configure a long
command in a dedicated script that's easier to run from the command
line. It helps if you add these scripts to directories in your
As this annoyance is related to the command-line interface, the annoyance is described only from the point of view of a Linux administrator. Any Linux user who is comfortable with the command-line interface can also use the lessons from this annoyance.
When you run a long command for the first time, it takes work. You may have read through the associated manpages to find the right arguments. You may have searched through your system to find the directory with the command you need.
You may not run a command like the following very often:
/home/michael/Desktop/scripts/dbmanage -opcg /home/michael/Desktop/process/logwriter
If you have to rerun the command again, you may not remember the function of the -o, -p, -c, and -g switches. You might not remember the directory with the hypothetical dbmanage command ...