From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Fourhundred Thecat <400thecat@gmx.ch>
Cc: zsh-users@zsh.org
Subject: Re: hostname completion for ssh / scp
Date: Sat, 5 Nov 2016 20:31:31 +0000 [thread overview]
Message-ID: <20161105203131.GA11681@fujitsu.shahaf.local2> (raw)
In-Reply-To: <581E2AE5.4040006__46101.1380576112$1478372966$gmane$org@gmx.ch>
Fourhundred Thecat wrote on Sat, Nov 05, 2016 at 19:54:29 +0100:
> > 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.
The IP address is mandatory on both Linux and FreeBSD, according to
their respective hosts(5) man pages.
Does hosts(5) on your system make the IP address optional? Or are you
simply saying that you put in /etc/hosts a line with no IP address, and
bash's hostname completion used hostnames from that line?
> 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>
next prev parent reply other threads:[~2016-11-05 20:31 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
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 [this message]
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=20161105203131.GA11681@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=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).