[Bash-completion-devel] I don't think this is a bug, that is why I am sending you a mail

[Igor Murzov]

> I don't think this is a bug, that is why I am sending you a mail, because
> it is too much for your bugreports, and I think it is more of  a "me"
> problem, and a software problem. And I have worked so HARD to make this
> work, so I hope you take your time to look through the data I send with
> you, because I guess you can easily pinpoint it. And I NEED this! I am
> supposed to have a whole lot of stuff going on, where this will help me.
> 
> 
> There is one thing with this I ought to tell you right away, and that is,
> that I am having bash installed as login shell, correctly, but Snow Leopard
> didn't ship with
> 
> My problem right now is this that it doesn't work at all; when I hit "ls"
> for instance I get this as a result:

By "it" you mean "bash-completion"? Does bash itself work as expected?

> ------------------------------------------------------------------
> -bash: /bin/ls: Argument list too long
> 878$
> 878$
> 878$ bash --version
> -bash: /opt/local/bin/bash: Argument list too long
> ------------------------------------------------------------------
> 
>  I am using bash_complete Release 1.99 (downloaded 2 days ago)
> 
> I am using Mac Os X Snow Leopard Latest Patch 10.6.8
> 
> I am using " GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0)"
> 
> I use Terminal.app for Mac Os X Version 2.1.2 (273.1)  I have specified My
> terminal type to xterm-color. LC_ALL, and that are sent to the shell from
> the Terminal.app.
> 
> I'm sending both my .inputrc and my .bashrc, and I really hope you can and
> will help me!

Does completion work better without .bashrc ? You have lots of custom settings
in your .bashrc, probably some of them break completion.

> Thanks in advance!
> 
> Tommy Bollman /McUsr
> 
> My .bashrc looks like this, with your software in it, but then the
> keyboard, is almost hanging, the commandline interpreter not working.