Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: ericblake AT comcast DOT net (Eric Blake) To: Arend-Jan Westhoff , cygwin AT cygwin DOT com Subject: tab-completion [was: VIM - Vi IMproved 6.4 (2005 Oct 15, compiled Oct 17 2005 11:54:34] Date: Wed, 26 Oct 2005 04:03:07 +0000 Message-Id: <102620050403.10186.435EFFFB0008D28F000027CA22007374780A050E040D0C079D0A@comcast.net> > PS Speaking of filename completion: Windows can be configured to use TAB as > cmd file and directory expansion character. I do find the cmd filename > completion behaviour more convenient than the default bash version. It is > usually > not difficult to organize a directory so that TAB or SHIFT-TAB find the > desired > file/dir quickly. > On bash you default get a beep and filename expansion stops whenever there > is more than one choice. I hate that. bash tab-completion is highly programmable. I suggest you read up on 'man bash' and 'man readline'. For example, binding TAB to 'menu-complete' instead of 'complete' changes the behavior of completion to cycle through complete filenames rather than stopping at the unambiguous prefix. Furthermore, with the bash-completion package installed properly, you get some very powerful context-sensitive completions (try doing THAT in windows). Just because the default behavior doesn't match your liking doesn't mean that bash can't do what you want. -- Eric Blake volunteer cygwin bash/bash-completion maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/