Re: [Bash-completion-devel] wget completion

2009-10-22 Thread gibboris
Reworked on the wget completion. One for bash4, the other backward compatible. If you look at the comments you'll see my philosophical questions / changelog : 1) For handling long options with bash4 : _longopt = ; compopt -o nospace Then at the beginning, before 'case ${prev}' :

Re: [Bash-completion-devel] wget completion

2009-04-14 Thread David Paleino
On Tue, 14 Apr 2009 09:31:55 +0200, David Paleino wrote: On Tue, 14 Apr 2009 00:19:21 +0200, gibbo...@gmail.com wrote: A small 'up' as I spent again some hours to get rid of these ':' completion problem [..] Maybe the 'scp' completion author would have an advice ? [..] Did you try

Re: [Bash-completion-devel] wget completion

2009-03-20 Thread gibboris
Thank you Freddy ! I put your modifications and looked at this nice _longopt(). It's far better in simplicity (even if I have the spaces appended to '=' as you warned me) - I *tried* the completion of the beginning of the host. But I can't get the -o nospace working :[ Another problem is that

Re: [Bash-completion-devel] wget completion

2009-03-20 Thread Freddy Vulto
On Fri, Mar 20, 2009 at 1:22 PM, gibbo...@gmail.com wrote: - I *tried* the completion of the beginning of the host. But I can't get the -o nospace working :[ You have to add the `-o nospace' option after `complete' instead of `compgen'. See diff. Another problem is that after 'http',

Re: [Bash-completion-devel] wget completion

2009-03-18 Thread Freddy Vulto
gibboris at gmail.com writes: Hello, I just tried a first attempt for the wget completion (see attachement). Here're some thoughts. See also proposed diff at the end. The `=' in long options isn't mandatory for wget, so I personally think you'd better leave them off as default suffix. The