zsh-users
 help / color / mirror / code / Atom feed
From: Fourhundred Thecat <400thecat@gmx.ch>
To: zsh-users@zsh.org
Subject: Re: hostname completion for ssh / scp
Date: Sat, 05 Nov 2016 19:54:29 +0100	[thread overview]
Message-ID: <581E2AE5.4040006@gmx.ch> (raw)
In-Reply-To: <161105102455.ZM20692@torch.brasslantern.com>

> On 2016-11-05 18:24, Bart Schaefer wrote:
> Well, yes.  The syntax of the /etc/hosts file is first an IP and then
> a hostname.  Somebody will possibly correct me, but I don't recall
> any valid use of /etc/hosts that has lines of host names without IPs.

Not true. IP address is not mandatory in /etc/hosts. You can leave it
out, and only have hostnames. This is useful for host autocompletion.
You don't have to type a long hostname, such as:

  ssh long-or-complicated-host.my-subdomain.my-domain.com

instead, you just type

  ssh long<TAB>

> } > If getent isn't returning anything useful, you can replace it:
> } > 
> } > zstyle ':completion:*:hosts' command 'cat /etc/hosts'
> } 
> } I would like to keep the completion from ~/.ssh/config and add
> } completion from /etc/hosts.
> 
> This shouldn't change the behavior with respect to ~/.ssh/config
> because that's read in _ssh_hosts rather than in _hosts where the
> style above applies.
> _hosts reads ~/.ssh/known_hosts whether or not the program named by
> the command style returns anything.
> 
> However, ~/.ssh/config will be skipped if the users-hosts tag finds
> any matching hosts, which is likely to happen if you are starting
> from a blank word, because users-hosts calls _hosts which will look
> in known_hosts.  If you start with a prefix on the line that matches
> a host in ~/.ssh/config and does NOT match one in ~/.ssh/known_hosts,
> you should get a completion.

yes that is correct.
But this is a terrible feature. The completion jumps to first matching
hostname, completely ignoring other matching hostnames.

  ssh s<TAB>

will complete to

  ssh server1.mydomain.com

and completely disregard

  system1.mydomain.com
  system2.mydomain.com

> 
> } > Note there have been several other fixes/improvements to ssh host-gathering
> } > since zsh 5.0.
> } 
> } can I simply copy Unix/_ssh from zsh 5.0. and use it on zsh 4.3.17 ?
> 
> I don't think so (you'd need at least _hosts as well) but in any case
> it wouldn't change anything because even 5.0+ is not expecting you to
> have just dumped a bunch of bare host names into /etc/hosts like that.
> 


  reply	other threads:[~2016-11-05 19:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 19:11 Fourhundred Thecat
2016-11-05  4:42 ` Bart Schaefer
2016-11-05  8:55   ` Fourhundred Thecat
2016-11-05 17:24     ` Bart Schaefer
2016-11-05 18:54       ` Fourhundred Thecat [this message]
2016-11-05 20:29         ` Bart Schaefer
2016-11-05 20:54           ` Fourhundred Thecat
2016-11-05 22:53           ` Bart Schaefer
2016-11-06  8:49             ` Fourhundred Thecat
2016-11-06 17:41               ` Bart Schaefer
     [not found]       ` <581E2AE5.4040006__46101.1380576112$1478372966$gmane$org@gmx.ch>
2016-11-05 20:31         ` Daniel Shahaf
2016-11-05 20:50           ` Fourhundred Thecat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=581E2AE5.4040006@gmx.ch \
    --to=400thecat@gmx.ch \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).