zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Jan Palus <jpalus@fastmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: zsh does not offer ssh host from config
Date: Sat, 10 Dec 2022 21:31:20 +0100	[thread overview]
Message-ID: <CAN=4vMo=TObHF7wrt7AXt=Sf5KRUGD3tEnVyMrWqACS_k54o0A@mail.gmail.com> (raw)
In-Reply-To: <20221210200602.ayy4d3yzd6vz52qc@pine.grzadka>

On Sat, Dec 10, 2022 at 9:06 PM Jan Palus <jpalus@fastmail.com> wrote:
>
> On 10.12.2022 13:08, Roman Perepelitsa wrote:
> >
> > If you only ever ssh to hosts listed in the ssh config, you can
> > configure ssh completions to respect that:
> >
> >     zstyle ':completion:*:(ssh|scp):*:hosts' hosts
> >
> > Listing all remote machines in the ssh config has other advantages
> > besides making completions more predictable.
>
>
> It's nice to have a possibility to customize behavior but I'd say more
> sensible default would be to offer both.

Oh, I'm not arguing in favor of the current implementation. I just
thought it might be useful to mention the setup I've made for myself
that works decently well.

> In my case it's much more practical to ie use pattern in ssh config for
> all the test envs instead of listing plenty of them explicitly.

I used to do that but then switched to my current setup where the ssh
config contains all remote machines (I generate it with a script). I
really like the ability to list all machines with a TAB. That said, I
can imagine environments where this kind of setup isn't possible.

Roman.


  reply	other threads:[~2022-12-10 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09  1:06 Jan Palus
2022-12-10 12:01 ` Daniel Shahaf
2022-12-10 12:08 ` Roman Perepelitsa
2022-12-10 20:06   ` Jan Palus
2022-12-10 20:31     ` Roman Perepelitsa [this message]
2022-12-10 20:49       ` Bart Schaefer

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='CAN=4vMo=TObHF7wrt7AXt=Sf5KRUGD3tEnVyMrWqACS_k54o0A@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --cc=jpalus@fastmail.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).