{"id":30,"date":"2008-08-24T20:08:02","date_gmt":"2008-08-25T00:08:02","guid":{"rendered":"http:\/\/www.compdigitec.com\/labs\/?p=30"},"modified":"2008-08-25T07:39:03","modified_gmt":"2008-08-25T11:39:03","slug":"aliases-for-common-command-line-typos","status":"publish","type":"post","link":"http:\/\/www.compdigitec.com\/labs\/2008\/08\/24\/aliases-for-common-command-line-typos\/","title":{"rendered":"Aliases for common command line typos"},"content":{"rendered":"

Update (2008-08-25): Lists complete and ready for download.<\/strong>
\nUpdate (2008-08-24): The list may take some time to compile, so downloads may not be available until August 25.<\/span><\/p>\n

Are you tired from “bash: somethinghere<\/span>: command not found<\/span>” errors that happen when you type something like vf instead of cd<\/a>, or cla instead of cls (alias for clear)? Well, now you can prevent it, because we have composed a list of most common command line typos<\/a>. You won’t<\/strong> be able to use these aliases on Microsoft Windows due to cmd.exe<\/a> not supporting aliases (unlike bash<\/a>). You can<\/strong>, however, use these with Cygwin<\/a> bash.<\/p>\n

To use it, download the first download for each command and add to your ~\/.bashrc. If you’re feeling a bit adventurous, you can download the CSV version (line 1 = command name, followed by one word for each typo) and parse it with Compdigitec FlatfileTools<\/a>. If you don’t know how, read the article on it<\/a>. Note: both the alias list and the CSV version use UNIX\/Linux encoding (\\n).<\/span><\/p>\n

Typographical errors of the ls command<\/a>.<\/span> You can download the list of aliases<\/a> or the CSV version<\/a>.<\/p>\n