It seems that $COMP_WORDBREAKS annoys users when filenames contain one of its characters: http://lists.gnu.org/archive/html/bug-bash/2005-07/msg00034.html http://lists.gnu.org/archive/html/bug-bash/2006-09/msg00019.html http://lists.gnu.org/archive/html/bug-bash/2011-02/msg00163.html and my bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674084
Unsetting $COMP_WORDBREAKS is not a solution, as completion would no longer work in contexts where such characters are word separators. How about the following behavior when the user types [TAB]? 1. Try to complete the whole word, ignoring $COMP_WORDBREAKS. 2. If there are no matches, take $COMP_WORDBREAKS into account like now. I suppose that false positives for (1) are rare enough, so that this heuristic would work well in practice. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
