Re: ssh config "Include" and bash completion

2018-05-14 Thread Javier Barroso
Hello Greg, On Mon, May 14, 2018 at 3:35 PM, Greg Wooledge wrote: > On Mon, May 14, 2018 at 03:29:22PM +0200, Javier Barroso wrote: >> Maybe you can improve the script talking / sendind pull request? with >> żupstream? żhttps://github.com/scop/bash-completion? >> >> Thank you ! > > Not likely to

Re: ssh config "Include" and bash completion

2018-05-14 Thread Greg Wooledge
On Mon, May 14, 2018 at 03:29:22PM +0200, Javier Barroso wrote: > Maybe you can improve the script talking / sendind pull request? with > ¿upstream? ¿https://github.com/scop/bash-completion? > > Thank you ! Not likely to happen. > == OFF TOPIC == > An annoying bug on debian (at least for me): >

Re: ssh config "Include" and bash completion

2018-05-14 Thread Javier Barroso
Hello Greg, On Mon, May 14, 2018 at 3:19 PM, Greg Wooledge wrote: >> local included=$( command sed -ne >> 's/^[[:blank:]]*[Ii][Nn][Cc][Ll][Uu][Dd][Ee][[:blank:]]\{1,\}\([^#%]*\)\(#.*\)\{0,1\}$/\1/p' >> "${configfile}" ) > > So, "included" is a string variable containing the ouput of sed. > >

Re: ssh config "Include" and bash completion

2018-05-14 Thread Greg Wooledge
> local included=$( command sed -ne > 's/^[[:blank:]]*[Ii][Nn][Cc][Ll][Uu][Dd][Ee][[:blank:]]\{1,\}\([^#%]*\)\(#.*\)\{0,1\}$/\1/p' > "${configfile}" ) So, "included" is a string variable containing the ouput of sed. If I'm reading that regex correctly, there'll be one pathname per line. >

Re: ssh config "Include" and bash completion

2018-05-14 Thread Richard Hector
On 14/05/18 21:51, Javier Barroso wrote: > Hello Hector, > > It work for me: > > $ grep "Include\|testing" /etc/ssh/ssh_config ; cat /etc/ssh/ssh.d/test > Include /etc/ssh/ssh.d/test > Host testing > Hostname 1.1.1.1 > > $ ssh test => testing > $ dpkg -l bash-completion > Deseado=desconocido(U)/

Re: ssh config "Include" and bash completion

2018-05-14 Thread Richard Hector
On 14/05/18 18:09, Richard Hector wrote: > Hi all, > > I recently started using the Include directive in my .ssh/config file - > so all the definitions are now in .ssh/config.d/. > > Now bash completion of hostnames no longer works. Is this expected > behaviour? Anyone know how to fix it, without

Re: ssh config "Include" and bash completion

2018-05-14 Thread Javier Barroso
On Mon, May 14, 2018 at 11:51 AM, Javier Barroso wrote: > Hello Hector, > > It work for me: > > $ grep "Include\|testing" /etc/ssh/ssh_config ; cat /etc/ssh/ssh.d/test > Include /etc/ssh/ssh.d/test > Host testing > Hostname 1.1.1.1 > > $ ssh test => testing > $ dpkg -l bash-completion > Deseado=de

Re: ssh config "Include" and bash completion

2018-05-14 Thread Javier Barroso
Hello Hector, It work for me: $ grep "Include\|testing" /etc/ssh/ssh_config ; cat /etc/ssh/ssh.d/test Include /etc/ssh/ssh.d/test Host testing Hostname 1.1.1.1 $ ssh test => testing $ dpkg -l bash-completion Deseado=desconocido(U)/Instalar/eliminaR/Purgar/retener(H) | Estado=No/Inst/ficheros-Co

Re: ssh config "Include" and bash completion

2018-05-14 Thread Richard Hector
On 14/05/18 20:49, john doe wrote: > On 5/14/2018 8:09 AM, Richard Hector wrote: >> Hi all, >> >> I recently started using the Include directive in my .ssh/config file - >> so all the definitions are now in .ssh/config.d/. >> >> Now bash completion of hostnames no longer works. Is this expected >>

Re: ssh config "Include" and bash completion

2018-05-14 Thread john doe
On 5/14/2018 8:09 AM, Richard Hector wrote: Hi all, I recently started using the Include directive in my .ssh/config file - so all the definitions are now in .ssh/config.d/. Now bash completion of hostnames no longer works. Is this expected behaviour? Anyone know how to fix it, without revertin

ssh config "Include" and bash completion

2018-05-13 Thread Richard Hector
Hi all, I recently started using the Include directive in my .ssh/config file - so all the definitions are now in .ssh/config.d/. Now bash completion of hostnames no longer works. Is this expected behaviour? Anyone know how to fix it, without reverting to a single file? I couldn't work out how t