Sorry for the long delay in responding, I've been swamped. I tried your suggestion and it WAS something in my shell. I tracked it down and the problem is:
set -o allexport That has been in our .bashrc for a very long time. I've preserved it just because it was there when I started and I didn't want to change things. I'll have to investigate if removing it will break anything. Thanks! Dan On Mon, 2010-09-20 at 16:28 -0400, Adam Weinberger wrote: > Dan - > > Another committer is restoring the old bash-completion (due to the > shell freezing on amd64). It will live in > shells/bash-completion-classic. Once that port gets updated, give it a > try and see if it fixes your problem. > > Create a new user and make a .bashrc that contains only > > source /usr/local/etc/bash_completion > > and see if the problem persists. If it does, check for any odd > definitions in /etc/make.conf and /etc/profile. If the problem > disappears, you have something strange in your .bashrc. > > # Adam > > > On 20 September 2010 11:29, Dan D Niles <d...@more.net> wrote: > > > > 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 <d...@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 > >> > > >> > > >> > > >> > >> > >> > > > > > > > > > _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel