[Bash-completion-devel] Interesting problem with bash-completion

[Dan D Niles]

I have the newest versions of bash and bash-completions that are in the
ports tree:

bash-4.1.7_2                =  up-to-date with port 
bash-completion-1.2_1,1     =  up-to-date with port 

I have the problem on 7.1, 7.3, and 8.1.  I haven't checked anywhere
else.

Dan

On Sat, 2010-09-18 at 17:59 -0400, Adam Weinberger wrote:
> Dan -
> 
> That is certainly unusual. What version of bash do you have installed?
> I cannot replicate your problem.
> 
> # Adam
> 
> 
> On 17 September 2010 15:04, Dan D Niles <dan at more.net> wrote:
> > I use bash-completion on my ubuntu desktop and it works fine.  I've
> > added it to my FreeBSD servers, and I have an odd problem.  When I su or
> > run other scripts I get some weird errors.  I can duplication the errors
> > with just 'exec bash':
> >
> > # exec bash
> > bash: _python: line 16: syntax error near unexpected token `('
> > bash: _python: line 16: ` !(python|-?))'
> > bash: error importing function definition for `_python'
> > bash: _xz: line 15: syntax error near unexpected token `('
> > bash: _xz: line 15: ` --decompress | --list | --test | -!(-*)[dlt]*)'
> > bash: error importing function definition for `_xz'
> > bash: _tar: line 8: syntax error near unexpected token `('
> > bash: _tar: line 8: ` ?(-)[cr]*f)'
> > bash: error importing function definition for `_tar'
> >
> > As far as I can tell, the syntax it is complaining about is valid.  It
> > does not complain the first time the shell starts.  I'm quite baffled.
> >
> > I would be happy to provide more info or try some stuff out.
> >
> > Thanks,
> >
> > Dan
> >
> >
> >
> 
> 
>