On Mon, 9 Jul 2012 18:16:51 +0200 Tommy Bollman <tommy.boll...@gmail.com> wrote:
> Hello Igor! > > I can try, where do I find version 2.0? http://bash-completion.alioth.debian.org/files/bash-completion-2.0.tar.bz2 -- Igor > Cheers > > Tommy > > 2012/7/9 Igor Murzov <e-m...@date.by> > > > > Hello Igor! > > > > > > Thanks for answering. > > > > > > 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. > > > > > > 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. > > > > > > 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. > > > > > > 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… > > > Below is the output, showing you the result when *only* version 1.99 is > > > involved: > > > > Can you test version 2.0? It has some fixes to filename completion. > > If you have free time, then you can bisect the issue, that would be > > most helpful. > > > > > 895$ ls > > > ls lsbom lsdistcc lsg lsm lsof lsvfs > > > 895$ ls > > > ls lsbom lsdistcc lsg lsm lsof lsvfs > > > 895$ ls *l > > > -bash: /bin/ls: Argument list too long > > > > > > 896$ ls * > > > -bash: /bin/ls: Argument list too long > > > 897$ vim * > > > Display all 186 possibilities? (y or n) > > > 897$ vim cd prj > > > -bash: /Users/tommybollman/bin/vim: Argument list too long > > > 898$ cd Prj > > > /Users/tommybollman/Documents/Prj > > > 899$ ls > > > -bash: /bin/ls: Argument list too long > > > 899$ ls > > > -bash: /bin/ls: Argument list too long > > > 900$ comple -r ls > > > -bash: comple: command not found > > > 901$ complete -r ls > > > -bash: complete: ls: no completion specification > > > 902$ Complete -r ls > > > -bash: Complete: command not found > > > 903$ ls > > > -bash: /bin/ls: Argument list too long > > > 903$ comple -r /bin/ls > > > -bash: comple: command not found > > > 904$ complet -r /bin/ls > > > -bash: complet: command not found > > > 905$ complete -r /bin/ls > > > -bash: complete: /bin/ls: no completion specification > > > 906$ ls > > > -bash: /bin/ls: Argument list too long > > > 906$ > > > > > > > > > > > > Cheers > > > > > > Tommy > > > > > > > > > 2012/7/9 Igor Murzov <e-m...@date.by> > > > > > > > > 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. > > > > > > _______________________________________________ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel