bash-completion populate with data?

[Joveice]

Hello, is there any way for me to populate bash-completion with a list of server names, so when I want to ssh I can just write parts of it and tab the rest? The list I got is quite large.

[Master Disaster]

7 minutes ago, Joveice said:

Hello, is there any way for me to populate bash-completion with a list of server names, so when I want to ssh I can just write parts of it and tab the rest? The list I got is quite large.

Not to my knowledge, if it was me I'd write a script with the list in it so when you run it will ask which server to connect to but I don't consider myself a Linux expert so I'd recommend you wait for someone more experienced than me to chime in.

[Joveice]

1 minute ago, Master Disaster said:

Not to my knowledge, if it was me I'd write a script with the list in it so when you run it will ask which server to connect to but I don't consider myself a Linux expert so I'd recommend you wait for someone more experienced than me to chime in.

I mean, I could ask everyone around me (at work) but they all are doing stuff, I'm just doing small tasks and tweaks with a bit of free time to learn on my own. I guess I could also just script it to open a ssh connection to all the servers, then it would populate that packages. (Probably not all at once heh :P)

[Fetzie]

7 hours ago, Joveice said:

Hello, is there any way for me to populate bash-completion with a list of server names, so when I want to ssh I can just write parts of it and tab the rest? The list I got is quite large.

You could make a load of bash scripts that execute the ssh command to the specific server, and put them in /usr/local/bin/ if all users should have access to the commands or in $HOME/bin/ if you only want you to have access to them.

 

If you want to use $HOME/bin then it may require creation and adding to the path:

 

# mkdir ${HOME}/bin
# echo 'export PATH="${PATH}:${HOME}/bin"' >> ${HOME}/.bashrc
# now relog so $PATH is updated
# now create a script in ${HOME}/bin and make it executable
  

 

That way you don't need to type the path to the script, you can just run it as

ssh_test.sh

and it will work with auto-completion from any location in the FS as the scripts are in your $PATH.

[Joveice]

2 hours ago, Fetzie said:

You could make a load of bash scripts that execute the ssh command to the specific server, and put them in /usr/local/bin/ if all users should have access to the commands or in $HOME/bin/ if you only want you to have access to them.

 

If you want to use $HOME/bin then it may require creation and adding to the path:

 

# mkdir ${HOME}/bin
# echo 'export PATH="${PATH}:${HOME}/bin"' >> ${HOME}/.bashrc
# now relog so $PATH is updated
# now create a script in ${HOME}/bin and make it executable
  

 

That way you don't need to type the path to the script, you can just run it as

ssh_test.sh

and it will work with auto-completion from any location in the FS as the scripts are in your $PATH.

Yea, but I'm already using the package bash-completion, I just wanted to know if I could populate it with data

[Sauron]

3 hours ago, Fetzie said:

You could make a load of bash scripts that execute the ssh command to the specific server, and put them in /usr/local/bin/ if all users should have access to the commands or in $HOME/bin/ if you only want you to have access to them.

 

If you want to use $HOME/bin then it may require creation and adding to the path:

 

# mkdir ${HOME}/bin
# echo 'export PATH="${PATH}:${HOME}/bin"' >> ${HOME}/.bashrc
# now relog so $PATH is updated
# now create a script in ${HOME}/bin and make it executable
  

 

That way you don't need to type the path to the script, you can just run it as

ssh_test.sh

and it will work with auto-completion from any location in the FS as the scripts are in your $PATH.

This is a good idea, but it's much better to use an alias in /home/yourname/.bashrc:

alias myserver="ssh username@address"

This accomplishes a few things:

1) the alias will autocomplete in the shell

2) you aren't touching system directories

3) it's faster than creating a bunch of .sh files and making them executable

[Fleetscut]

i believe there is a way to define your own bash completion scripts. look up bash_completion.d. There is also a way to specify server connection settings in an ssh config file so you just need to type "ssh something" and it will pull all the settings out of the config and auto connect.

[Fetzie]

1 hour ago, Sauron said:

This is a good idea, but it's much better to use an alias in /home/yourname/.bashrc:

alias myserver="ssh username@address"

This accomplishes a few things:

1) the alias will autocomplete in the shell

2) you aren't touching system directories

3) it's faster than creating a bunch of .sh files and making them executable

Case 1: fair enough

Although for case 2, the directory /usr/local/bin/ exists for precisely this purpose and for case 3 I'd script the script creation (no way in hell I'm typing out dozens of almost identical things)

25 minutes ago, Fleetscut said:

i believe there is a way to define your own bash completion scripts. look up bash_completion.d. There is also a way to specify server connection settings in an ssh config file so you just need to type "ssh something" and it will pull all the settings out of the config and auto connect.

You can define aliases in $HOME/.bash_aliases (use a loop to save some time by reading the server names from a file :)).

 

#!/bin/bash

while read foo; do
	bar ${foo};
done < servers.txt

 

[Sauron]

1 hour ago, Fetzie said:

Although for case 2, the directory /usr/local/bin/ exists for precisely this purpose and for case 3 I'd script the script creation (no way in hell I'm typing out dozens of almost identical things)

That's true, personally I find aliases to be less "messy" but I suppose shell scripts work too. There is another small advantage to aliases though - it's (slightly) easier to migrate a single .bashrc file than a bunch of .sh files from /usr/local/bin.

[Epictek300]

Zsh has this built in.