Package: bash Version: 3.1dfsg-8 Severity: normal complete-into-braces, as documented, performs filename completion. This is quite awkwards, since when a programmable completion is available, it means in many cases that filenames are not valid completions.
I do agree that it would not be reasonable to expand to all possible completions, since eg. it would be pointless to expand all possible option flags - this example shows that the problem is not trivial to handle. OTOH, it would seem that a first intermediary step would be useful, by allowing brace completion of everything returned by the pgorammable completion, that does not start with a hyphen. For cases where it does make sense, it is a huge usability improvement, and for cases where it does not, it is likely not to make less sense than brace-completing filenames - anyway, as today, the user can undo the expansion if it does not fit. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages bash depends on: ii base-files 4.0.2 Debian base system miscellaneous f ii debianutils 2.28.2 Miscellaneous utilities specific t ii libc6 2.7-6 GNU C Library: Shared libraries ii libncurses5 5.6+20080119-1 Shared libraries for terminal hand bash recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
