-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: completions from known_hosts for ssh and ping on non-default port #175
Comments
Ok, thanks, I understand that the behavior isn't what you want. Please also describe the behavior that you do want. 🙂
Also, should Also, sharing sample I've never used |
For ssh, if the port is non default, I think it should suggest -p <port_num> from the relevant line in Sample known_hosts:
Sample .ssh/config file:
|
The ssh completions include only the first host in each host definition line in the .ssh/config file. (after ignoring wildcards, etc) Shouldn't it include all hosts in each host definition list in the .ssh/config file? (after ignoring wildcards, etc) Here is the completion list if it instead includes all the known hosts: I plan to make it list all the known hosts. P.S. Would it be preferable to list alphanumeric names before numeric IP addresses? |
Yeah, I'd want to have all.
I guess I have a lot of saved IPs and names.
P.S. Why is it showing different colors in your example? |
Cool! Done.
Cool, I'll leave it as-is.
I made it use the "alias" match type for addresses from .ssh/config (uses the (And for ping addresses from the hosts file use the default terminal color.) |
Entries of non-default ports in .ssh/known_hosts are saved as:
When using
ping
orssh
completions, they are shown as:ssh [192.168.1.222
andping [192.168.1.222
The text was updated successfully, but these errors were encountered: