Re: [Bash-completion-devel] _filedir only escaping whitespace when `-o filenames' is in effect?

2009-08-12 Thread Ville Skyttä
On Monday 03 August 2009, Freddy Vulto wrote: I don't see how `-o plusdirs' is going to save us here? It probably doesn't - I just mentioned it in a context where I suggested current _filedir would be pretty much obsolete if we could assume -o plusdirs could be used everywhere. So I think

Re: [Bash-completion-devel] _filedir only escaping whitespace when `-o filenames' is in effect?

2009-08-03 Thread Freddy Vulto
On Sun, Aug 2, 2009 at 9:23 PM, Ville Skyttäville.sky...@iki.fi wrote: ...but why wouldn't simply adding $filenames to their complete calls be the right thing to do?  The above sounds somewhat messy to me and personally I'd rather start thinking about getting rid of most of _filedir's current

Re: [Bash-completion-devel] _filedir only escaping whitespace when `-o filenames' is in effect?

2009-08-02 Thread Ville Skyttä
On Tuesday 28 July 2009, Freddy Vulto wrote: I was under the assumption that `_filedir' was to be trusted anywhere, but it seems it isn't or am I overlooking something? I think it isn't... Otherwise, wouldn't it be nice to add an option to `_filedir' to escape spaces? Or better, create a

[Bash-completion-devel] _filedir only escaping whitespace when `-o filenames' is in effect?

2009-07-27 Thread Freddy Vulto
I just noticed `ssh -F TAB' doesn't escape spaces in filenames. Further investigation showes that _filedir only works if `-o filenames' is in effect: $ touch 'a b' $ _foo() { cur=$(_get_cword); _filedir; } $ complete -F _foo foo $ foo aTAB $ foo a b # Incorrect, space isn't