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


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

Re: How to apply Bash completion usefully and more practically

Started byChet Ramey <chet.ramey@case.edu>
First post2018-02-26 09:07 -0500
Last post2018-02-26 09:07 -0500
Articles 1 — 1 participant

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: How to apply Bash completion usefully and more practically Chet Ramey <chet.ramey@case.edu> - 2018-02-26 09:07 -0500

#13746 — Re: How to apply Bash completion usefully and more practically

FromChet Ramey <chet.ramey@case.edu>
Date2018-02-26 09:07 -0500
SubjectRe: How to apply Bash completion usefully and more practically
Message-ID<mailman.9747.1519654055.27995.bug-bash@gnu.org>
On 2/25/18 5:01 AM, Budi wrote:
> How to apply Bash completion in more useful way.
> If TAB key is pressed Bash just show a list of corresponding command, I
> thought it will scroll over all corresponding command on which the cursor
> of shell prompt is active. (just like traditional Windows cmd prompt)
> How to make it able to perform such ? Thanks so much in advance

If I understand this correctly, you want the default to be what readline
calls `menu completion'. You can bind tab to menu-complete to get what I
think you want:

bind 'TAB:menu-complete'

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

[toc] | [standalone]


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


csiph-web