×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

2.8 seconds of hate - bash-completion

Qzukk (229616) writes | about 6 months ago

User Journal 1

In an effort to be fancy and helpful, bash now has context aware tab completion (in the bash-completion package on Debian). Based on where you are and what command you're typing, pressing tab will Do (what the completion script writer thought was) The Right Thing.

Unless what you think is the right thing was was the behavior of older versions of bash where you could do

**/*.c<Tab><Tab>

In an effort to be fancy and helpful, bash now has context aware tab completion (in the bash-completion package on Debian). Based on where you are and what command you're typing, pressing tab will Do (what the completion script writer thought was) The Right Thing.

Unless what you think is the right thing was was the behavior of older versions of bash where you could do

**/*.c<Tab><Tab>

and (eventually, ** is damn slow) get a list of all of the matching files. It also worked with [...] {...} ? or any of the other bash wildcards. You know, just in case you wanted to see what your command is going to do before you hit enter.

Now I have to ^U, ls ^Y, then ^Y, which takes about 2.8 seconds (including the realization that bash is just going to keep beeping at me if I keep hitting tab). Or disable fancy and helpful completion with complete -r

1 comment

Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Sign up for Slashdot Newsletters
Create a Slashdot Account

Loading...