2.1 also has a whole bunch of extra errors that don't crop up in 1.3: -bash: declare: -A: invalid option declare: usage: declare [-afFirtx] [-p] [name[=value] ...] -bash: complete: -D: invalid option complete: usage: complete [-abcdefgjksuv] [-pr] [-o option] [-A action] [-G globpat] [-W wordlist] [-P prefix] [-S suffix] [-X filterpat] [-F function] [-C command] [name ...]
On Fri, Feb 28, 2014 at 11:40 AM, Giordon Stark <[email protected]> wrote: > This is also broken in 2.1 -- if you run with export POSIXLY_CORRECT=1 -- > you will see that the regexes using the tabs don't work at all. > > Giordon > > > On Fri, Feb 28, 2014 at 6:38 AM, Ville Skyttä <[email protected]> wrote: > >> On Fri, Feb 28, 2014 at 9:11 AM, Giordon Stark <[email protected]> wrote: >> > Hey all - it appears that the problem lies with BSD sed and Mac OSX's >> sed >> > doesn't support tabs in the same way as you're using them. >> >> s/you're/you were/ :) >> >> This problem and several similar ones have to my knowledge been fixed >> in current bash-completion versions. 2.1 is the latest release at the >> moment, 1.3 is already three years old and the 1.x branch almost >> certainly won't receive any more updates/fixes. >> > >
_______________________________________________ Bash-completion-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel
