| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
https://www.freebsd.org/cgi/man.cgi?query=ssh_config&sektion=5
1. It is possible to add multiple whitespace characters between the keyword (i.e. Host) and the argument(s).
2. It is allowed to have a single = and whitespace between the keyword and the argument(s).
3. It is possible to add multiple host names under a single Host directive by spacing the names apart.
1. and 3. are actual conventions that we use in our team, and I couldn't get auto-complete working for fish without this modification.
Modification explained:
a. The space between Host(?:name)? and the \w.* was replaced by (?:\s+|\s*=\s*) to match any sequence of whitespace characters, or optional whitespaces with a single =, per spec.
b. Result of first replacement is piped through another string replace to switch duplicate whitespace characters to a single space, and then piped to be split by that space. This allows specifying several aliases or host names in a single Host/Hostname definition, also per spec.
|
|
|
|
|
|
|
|
| |
I believe apm must have been buggy - example output that I found online
showed `tr` was mangling paths with spaces in it. Should be fixed.
Also, use dscl on OS X in __fish_complete_users.fish like
__fish_print_users.fish already does.
|
|
|
|
| |
Fixes #2843
|
|
|
|
|
|
|
|
| |
These are an additional source of information
Thanks to @sysbot (#2313) for the inspiration.
This also stringifies the ssh_config reading
|
| |
|
| |
|
|
|
|
| |
This would be a lot of useless options for those who block via hosts.
|
|
|
|
|
|
|
|
|
| |
This is to the benefit of systems with ancient GNU sed, which does not
recognize "-E", but only "-r".
Fixes #2305 - even if it doesn't replace all `sed -E` invocations in the
codebase, the others are unlikely to occur on CentOS and other similarly
crusty systems.
|
|
|
|
| |
Makes it harder to cause issues with aliases, see fish-shell#2245
|
|
|
|
| |
Closes #2137.
|
|
|
|
|
|
| |
Uses awk rather than sed to account for multiple formatting options.
Closes #1260.
|
|
|
|
| |
See the PATTERNS section of ssh_config(5) for wildcards supported by ssh.
|
|
|
|
| |
refs https://github.com/fish-shell/fish-shell/issues/1355
|
|
|
|
| |
addition to user config.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Valid DNS names cannot have a | character and hashed ssh hosts
always begin with the | character. Therefore we ignore lines that
begin with |.
Signed-off-by: Greg Dietsche <Gregory.Dietsche@cuw.edu>
|
|
|
|
| |
Signed-off-by: Greg Dietsche <Gregory.Dietsche@cuw.edu>
|
| |
|
| |
|
| |
|
|
|
|
| |
of /etc/hosts
|
|
|
|
|
|
| |
sources of information, but ~/.ssh/config may also be useful. Gather all of the 'Host' declarations from ~/.ssh/config and filter out the ones with wildcards. Signed-off-by: James Vega <jamessan@debian.org>
darcs-hash:20090202210242-ac50b-cf50070ee33ab6113e32a4d997d464ac4b1faf24.gz
|
|
|
|
|
|
| |
that strips away any GREP_OPTIONS. This is needed to avoid users who have added arbitrary switches to GREP_OPTIONS, thus changing its behaviour.
darcs-hash:20061129140004-ac50b-485ff6bfd71e9459ba62461f6e093ca5c9ddd664.gz
|
|
darcs-hash:20060217101339-ac50b-d93d2c620a4b7f75f05ff461a6edbee001da7613.gz
|