zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: scp completion options
Date: Thu, 28 Jun 2018 13:26:10 -0700	[thread overview]
Message-ID: <CAH+w=7Y9KFiwRyAE_h1e1WBgm5wUKTPHq2G7iG-m8G7w0WZ1gQ@mail.gmail.com> (raw)
In-Reply-To: <20180628201457.GG21870@blackswan>

On Thu, Jun 28, 2018 at 1:14 PM, David Woodfall <dave@dawoodfall.net> 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.)


  reply	other threads:[~2018-06-28 20:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180626231957epcas4p275197b8b1b133496936cd1e2a59d15b6@epcas4p2.samsung.com>
2018-06-26 23:06 ` David Woodfall
2018-06-27  8:15   ` Peter Stephenson
2018-06-27 10:13     ` David Woodfall
2018-06-28  8:38       ` Peter Stephenson
2018-06-28 20:14         ` David Woodfall
2018-06-28 20:26           ` Bart Schaefer [this message]
2018-06-28 20:56             ` David Woodfall
2018-06-29  0:31               ` Bart Schaefer
2018-06-29  2:31                 ` David Woodfall
2018-08-20 14:51                 ` David Woodfall
     [not found]   ` <20180627091514.22955a04@camnpupstephen.cam.scsc.local>
2018-06-29  8:33     ` Peter Stephenson

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='CAH+w=7Y9KFiwRyAE_h1e1WBgm5wUKTPHq2G7iG-m8G7w0WZ1gQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --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).