Making a better, prettier, more functional Windows Command Line

Re:Making a better, prettier, more functional Windows Comman... by steven2012 on Wednesday July 17, 2013 @11:01AM (#6058019)

Personally I love the "cycle through the options" of the Windows Command Line. It's the one thing that I wish bash could emulate, instead of the "Show me all the options". For me, it's a lot more functional, because it doesn't require me to figure out what the differences are between file names. For example, trying to find the difference between R0BCRWPY_1373654012 vs R0BCRWPY_1373647568 is very tedious, especially if you have a bunch of similarly named files.

[ Parent | on HN ]

Re:Making a better, prettier, more functional Windows Comman... by sigil on Wednesday July 17, 2013 @11:04AM (#6058048)

It's possible in bash too. In your .bashrc:

    # tab key: cycle through the list of partial matches
    bind "\C-I":menu-complete

    # ^p: traditional completion
    bind "\C-p":complete

[ Parent | on HN ]

Re:Making a better, prettier, more functional Windows Comman... by edvinbesic on Wednesday July 17, 2013 @11:51AM (#6058364)

Also, I have my Shift-TAB bound to menu-complete-reverse. The way I got it to work is to chuck these two lines into ~/.inputrc

  TAB: menu-complete
  "\e[Z": "\e-1\C-i"

The second line is the non-obvious one, can't remember where I found it. I wasn't able to get this to run unless it was in .inputrc though.

[ Parent | on HN ]