> 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/
