Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > gnu.bash.bug > #14164 > unrolled thread

why is dash confused with underscore in autocompletion?

Back to article view | Back to gnu.bash.bug

Contents

  why is dash confused with underscore in autocompletion? L A Walsh <bash@tlinx.org> - 2018-05-29 14:32 -0700

#14164 — why is dash confused with underscore in autocompletion?

I have 4 files in a dir:

  remove-oldver-rpms-in-dir.pl
  remove_mounted_lv
  remove_multiples
  remove_nocase_dupfonts

When I do autocomplete:

  > ls remo<TAB>                # I get all 4 files listed:
  remove-oldver-rpms-in-dir.pl* remove_mounted_lv*
  remove_multiples*             remove_nocase_dupfonts*
  > ls remove                   # and 'remo' is extended to 'remove'

(fine so far)

then I add a dash (or minus), '-' and hit <TAB> again.

I'd expect it to autocomplete the entire filename for
'remove-oldver-rpms-in-dir.pl' since it is the only file with a dash
after 'remove', but instead, bash prompts me again as though there
is some ambiguity between a dash and an underline.

But there isn't. Indeed, adding a '*' after the dash and ENTER, and
ls shows only 1 file.

Is there some setting I've forgotten I've set that is enabling this
behavior?  I can't think of why I'd want it, since I really do want
it to complete the 1st filename.  It also doesn't limit the words to
ones w/underscore after 'remove' if I add '_', it still lists
'remove-old...' as a completion option.

So why is this happening and how can I turn it off?

Thanks!

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web