[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: why is dash confused with underscore in autocompletion?

From: Eric Blake
Subject: Re: why is dash confused with underscore in autocompletion?
Date: Tue, 29 May 2018 16:50:44 -0500
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0

On 05/29/2018 04:32 PM, L A Walsh wrote:

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.

When you have case-insensitive completion, I _like_ having - and _ be treated as case-insensitive counterparts (at least on US keyboards, those two symbols are on the same key, and differ only on whether you used shift, the same as other case-insensitive comparisons such as b/B).

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?

Readline documents 'completion-map-case' and 'completion-ignore-case' as the two knobs used to fine-tune whether you are doing case-insensitive completion, and if so, whether -/_ are part of that case-insensitivity.

Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

reply via email to

[Prev in Thread] Current Thread [Next in Thread]