zsh-workers
 help / color / mirror / code / Atom feed
From: Moritz Bunkus <moritz@bunkus.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: ssh host completion: ~/.ssh/config vs /etc/hosts
Date: Tue, 11 Aug 2015 14:45:37 +0200	[thread overview]
Message-ID: <20150811124536.GA5160@bunkus.org> (raw)
In-Reply-To: <150810125039.ZM1691@torch.brasslantern.com>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Hey,

thanks for the pointer, Bart. Reverting the patch mentioned in

>     http://www.zsh.org/mla/users/2007/msg00233.html

restores the behavior I want (and which I find less confusing, to be
honest): »ssh testme-<TAB>« now lists both the entries from /etc/hosts
as well as those from ~/.ssh/config.

> It seems a bit odd that this kicks in when there is no user-name part
> in the word being completed.

Even adding user@ I would expect all possible hosts to be listed, not
just the ones from /etc/hosts… To me the current behavior looks like a
bug. Why should entries from /etc/hosts be exclusive in any shape or
form? What makes them more special?

Note that I'm not really arguing against what the user in msg00233.html
wants to do. I'm talking about ssh completion's default behavior. Solely
from the point of view of ease of use.

Kind regards,
mosu

[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-08-11 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10 10:33 Moritz Bunkus
2015-08-10 19:50 ` Bart Schaefer
2015-08-11 12:45   ` Moritz Bunkus [this message]
2015-08-11 16:19     ` Bart Schaefer
2015-08-15  0:34   ` Vincent Lefevre

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=20150811124536.GA5160@bunkus.org \
    --to=moritz@bunkus.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).