Re: "complete -o filenames" sometimes not working

On Mon, Nov 11, 2024 at 10:51 PM Grisha Levit wrote: > > If your goal is to have readline do the quoting for you > Yes this is what I want to do. > , without treating the completions as filenames, the next version of bash > (5.3, see the 'devel' branch in the git repo) will have the '-o fullqu

Re: "complete -o filenames" sometimes not working

On Sat, Nov 9, 2024, 07:41 Clark Wang wrote: > On Sat, Nov 9, 2024 at 1:48 AM Chet Ramey wrote: > > > > > OK. You asked for the completions to be treated as filenames. When > > readline displays the possible completions for filenames, it doesn't > > display the full pathname -- just the portion

Re: "complete -o filenames" sometimes not working

On 11/9/24 7:38 AM, Clark Wang wrote: On Sat, Nov 9, 2024 at 1:48 AM Chet Ramey > wrote: OK. You asked for the completions to be treated as filenames. When readline displays the possible completions for filenames, it doesn't display the full pathname -- j

Re: "complete -o filenames" sometimes not working

On Sat, Nov 9, 2024 at 1:48 AM Chet Ramey wrote: > > OK. You asked for the completions to be treated as filenames. When > readline displays the possible completions for filenames, it doesn't > display the full pathname -- just the portion after the final slash. > The words with ProxyCommand= are

Re: "complete -o filenames" sometimes not working

On 11/7/24 9:53 AM, Clark Wang wrote: See the following reproduce example: $ cat ssh_compspec COMP_WORDBREAKS=${COMP_WORDBREAKS//[=:]/} function _ssh() { local cur="$2" pre="$3" local options=( ProxyCommand='/usr/bin/nc -x host:port %h %p -X 5' ProxyCommand='/usr/bin