http://linsec.ca/blog/2008/11/14/tips-and-tricks-for-working-on-the-command-line/?utm_source=rss&utm_medium=rss&utm_campaign=tips-and-tricks-for-working-on-the-command-line You can have it right, or you can have it now. But you can't have it right now. Wed, 25 Jan 2012 20:33:14 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://linsec.ca/blog/2008/11/14/tips-and-tricks-for-working-on-the-command-line/comment-page-1/#comment-2706 Quentin Fri, 14 Nov 2008 16:00:26 +0000 http://linsec.ca/blog/2008/11/14/tips-and-tricks-for-working-on-the-command-line/#comment-2706 One thing I find _extremely_ useful is the history-search-forward and history-search-backward bash commands. I bind them to crtl-up and ctrl-down. So, for example, by just typing "cd " then ctrl-up/down, I can browse through previous commands beginning with "cd". I'm surprise this feature is so little known, it would be great if it was configured by default. The only problem is ctrl-up/down doesn't generate the same thing in putty or in a terminal through vnc, so I have to put 3 lines in .inputrc for each binding :( One thing I find _extremely_ useful is the history-search-forward and history-search-backward bash commands. I bind them to crtl-up and ctrl-down. So, for example, by just typing “cd ” then ctrl-up/down, I can browse through previous commands beginning with “cd”.
I’m surprise this feature is so little known, it would be great if it was configured by default.
The only problem is ctrl-up/down doesn’t generate the same thing in putty or in a terminal through vnc, so I have to put 3 lines in .inputrc for each binding

]]>