Hello Igor!<div><br></div><div>Thanks for answering.</div><div><br></div><div>Bash itself works perfectly. It also works with bash_completion 1.3 when I just change the path to the source files, and the bash_completion.d though it errs on a couple of items namely _python, xz and tar.</div>
<div><br></div><div>Well, I use bash version 4.x so I figured it was best to use the latest version, but the bash_completion, totally locks up every thing, (not having tried any meta key to bypass), when I have it sourced, it even locks up commands for which I have done a "complete -r" for.</div>
<div><br></div><div>I'll come back to you, doing one more test, as I have had some completion scripts sourced, that is not coming with the origin of the bash_completion package.</div><div><br></div><div>And as you have seen how I have done it, I have made my own etc: ~/etc and put it all under there, because packet managers on OsX these days, they don't play nice with the others…</div>
<div>Below is the output, showing you the result when *only* version 1.99 is involved:</div><div><br></div><div><div>895$ ls</div><div>ls lsbom lsdistcc lsg lsm lsof lsvfs</div><div>895$ ls</div>
<div>ls lsbom lsdistcc lsg lsm lsof lsvfs</div><div>895$ ls *l</div><div>-bash: /bin/ls: Argument list too long</div><div>896$ ls *</div><div>-bash: /bin/ls: Argument list too long</div><div>897$ vim *</div>
<div>Display all 186 possibilities? (y or n)</div><div>897$ vim cd prj</div><div>-bash: /Users/tommybollman/bin/vim: Argument list too long</div><div>898$ cd Prj</div><div>/Users/tommybollman/Documents/Prj</div><div>899$ ls</div>
<div>-bash: /bin/ls: Argument list too long</div><div>899$ ls </div><div>-bash: /bin/ls: Argument list too long</div><div>900$ comple -r ls</div><div>-bash: comple: command not found</div><div>901$ complete -r ls</div><div>
-bash: complete: ls: no completion specification</div><div>902$ Complete -r ls</div><div>-bash: Complete: command not found</div><div><div>903$ ls</div><div>-bash: /bin/ls: Argument list too long</div><div>903$ comple -r /bin/ls</div>
<div>-bash: comple: command not found</div><div>904$ complet -r /bin/ls</div><div>-bash: complet: command not found</div><div>905$ complete -r /bin/ls</div><div>-bash: complete: /bin/ls: no completion specification</div><div>
906$ ls</div><div>-bash: /bin/ls: Argument list too long</div><div>906$ </div></div></div><div><br></div><div><br></div><div><br></div><div>Cheers</div><div><br></div><div>Tommy</div><div><br></div><div><br><div class="gmail_quote">
2012/7/9 Igor Murzov <span dir="ltr"><<a href="mailto:e-mail@date.by" target="_blank">e-mail@date.by</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">> I don't think this is a bug, that is why I am sending you a mail, because<br>
> it is too much for your bugreports, and I think it is more of a "me"<br>
> problem, and a software problem. And I have worked so HARD to make this<br>
> work, so I hope you take your time to look through the data I send with<br>
> you, because I guess you can easily pinpoint it. And I NEED this! I am<br>
> supposed to have a whole lot of stuff going on, where this will help me.<br>
><br>
><br>
> There is one thing with this I ought to tell you right away, and that is,<br>
> that I am having bash installed as login shell, correctly, but Snow Leopard<br>
> didn't ship with<br>
><br>
> My problem right now is this that it doesn't work at all; when I hit "ls"<br>
> for instance I get this as a result:<br>
<br>
</div>By "it" you mean "bash-completion"? Does bash itself work as expected?<br>
<div class="im"><br>
> ------------------------------------------------------------------<br>
> -bash: /bin/ls: Argument list too long<br>
> 878$<br>
> 878$<br>
> 878$ bash --version<br>
> -bash: /opt/local/bin/bash: Argument list too long<br>
> ------------------------------------------------------------------<br>
><br>
> I am using bash_complete Release 1.99 (downloaded 2 days ago)<br>
><br>
> I am using Mac Os X Snow Leopard Latest Patch 10.6.8<br>
><br>
> I am using " GNU bash, version 4.2.29(2)-release (i386-apple-darwin10.8.0)"<br>
><br>
> I use Terminal.app for Mac Os X Version 2.1.2 (273.1) I have specified My<br>
> terminal type to xterm-color. LC_ALL, and that are sent to the shell from<br>
> the Terminal.app.<br>
><br>
> I'm sending both my .inputrc and my .bashrc, and I really hope you can and<br>
> will help me!<br>
<br>
</div>Does completion work better without .bashrc ? You have lots of custom settings<br>
in your .bashrc, probably some of them break completion.<br>
<div class="HOEnZb"><div class="h5"><br>
> Thanks in advance!<br>
><br>
> Tommy Bollman /McUsr<br>
><br>
> My .bashrc looks like this, with your software in it, but then the<br>
> keyboard, is almost hanging, the commandline interpreter not working.<br>
</div></div></blockquote></div><br></div>