Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: scp completion options
- X-seq: zsh-users 23514
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh Users <zsh-users@xxxxxxx>
- Subject: Re: scp completion options
- Date: Thu, 28 Jun 2018 13:26:10 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=nFNoHlRtdGoor8nmXlyfBGnxt/Wrjx+A5jaUbglnvDw=; b=ITm+01rUZ01GxVYNEkMQs5nicFB2d0IL+CMFsZMCAMJ/RcPn++oL2oy+oNRIbRFeGk 2EZ4rtIrqghoGEvySB7Mnak2Kl1tnY840I5btHOh5f0tFJwGWBUkM3b8lg3xHfIe7vK2 jG/FRIKyFhLDa2jrnpXYGc7UuT9Uvagfnny4B52SFi24iys91zRWMVZQJzBCNa5nIQP0 4WEEbyfwfEGzh4CnhafP0aj9s4dWvOK6LVXr6OSxB0v8pMe/FXWPgcy+PbQ39kIcKLIz 4wCFFAieOPBOqDLZvMjRGCH+Jv6qrqROOIdS2Zj+H7h46SSCsh19GsB4F/zxXZM81mc+ gwoA==
- In-reply-to: <20180628201457.GG21870@blackswan>
- List-help: <mailto:zsh-users-help@zsh.org>
- List-id: Zsh Users List <zsh-users.zsh.org>
- List-post: <mailto:zsh-users@zsh.org>
- List-unsubscribe: <mailto:zsh-users-unsubscribe@zsh.org>
- Mailing-list: contact zsh-users-help@xxxxxxx; run by ezmlm
- References: <CGME20180626231957epcas4p275197b8b1b133496936cd1e2a59d15b6@epcas4p2.samsung.com> <20180626230654.GK11049@blackswan> <20180627081516eucas1p200d804de13d1e5a4f7ea223ecb2d9c49~79k6870Wv1727517275eucas1p2j@eucas1p2.samsung.com> <20180627101312.GL11049@blackswan> <20180628083835eucas1p2cb57feab1bca1540ed0a89cd6e26b9bb~8RikRcvz81808218082eucas1p2p@eucas1p2.samsung.com> <20180628201457.GG21870@blackswan>
On Thu, Jun 28, 2018 at 1:14 PM, David Woodfall <dave@xxxxxxxxxxxxxx> wrote:
>
> I've still to discover why sometimes remote names get escape for no
> apparent reason. eg I have a patch on the remote named:
>
> 0001-fix-typo-in-rc.geomyidae-slackware-init-script.patch
>
> This is the first item completed after hitting tab, but it is listed
> as
>
> ^[k*^[\0001-fix-typo-in-rc.geomyidae-slackware-init-script.patch
This is probably something being spat out by your shell startup on the
remote host. Go through your .zshenv, .zshrc, etc. (or equivalent
files for other shell) on the remote host and make sure that nothing
writes output such as terminal control sequences when the standard
input is not a tty. (It could also be something in /etc/zshenv in
which case you're probably stuck unless you can become root on the
remote host.)
Messages sorted by:
Reverse Date,
Date,
Thread,
Author