[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Idea: *.p<TAB> completion
From: |
積丹尼 Dan Jacobson |
Subject: |
Re: Idea: *.p<TAB> completion |
Date: |
Mon, 02 Sep 2019 02:00:01 +0800 |
>>>>> "CR" == Chet Ramey <chet.ramey@case.edu> writes:
CR> On 9/1/19 11:10 AM, 積丹尼 Dan Jacobson wrote:
>> $ ls *.pdf
>> a.pdf b.pdf
>> $ diff *.p<TAB>
>>
>> At this point <TAB> should complete "*.pdf".
CR> It does (well, the default completion does, maybe programmable completion
CR> for diff does too). But the two possible completions differ immediately --
CR> in the first character -- so what are you going to do? Rather than remove
CR> the word, as normal completion would do, the default bash completion leaves
CR> it alone.
I'm saying I want a real "* . p d f" as the result, I.e., genuine * 0x2A
asterisk left sitting upon the screen.
diff is just an example. Maybe use the generic ":" command instead.
(Yes I wish to disable /usr/share/bash-completion effects while testing,
though it is on by default in Debian.)
>> Or maybe as a bonus it could complete "a.pdf b.pdf" via a different key.
CR> You want it to insert the possible completions? Use C-x* in emacs mode:
CR> glob-expand-word (C-x *)
CR> The word before point is treated as a pattern for pathname
CR> expansion, and the list of matching filenames is inserted,
CR> replacing the word. If a numeric argument is supplied, an
CR> asterisk is appended before pathname expansion.
Well that can deal with "*" but not "*.p".
Re: Idea: *.p<TAB> completion, Dennis Clarke, 2019/09/01