zsh-users
 help / color / mirror / code / Atom feed
From: Hannu Koivisto <azure@iki.fi>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: zsh-users@sunsite.dk
Subject: Re: Remote scp completion that can handle spaces etc. in pathnames
Date: Mon, 17 Feb 2003 11:18:38 +0200	[thread overview]
Message-ID: <87smunnu35.fsf@lynx.ionific.com> (raw)
In-Reply-To: <1815.1045152769@finches.logica.co.uk> (Oliver Kiddle's message of "Thu, 13 Feb 2003 17:12:49 +0100")

Oliver Kiddle <okiddle@yahoo.co.uk> writes:

> The completion for ssh uses ls -F on the remote machine to get the files
> and then takes trailing *, =, |, / and @ characters to be the characters

Ah, so it does indeed.  I wonder if listing could be done in some
other, more robust way.  The availability of programs on the remote
machine obviously limits the possible ways...  Perhaps find could
be used?

> added by ls -F to indicate the type of the file. I don't tend to have
> file names ending in those characters and find it useful that it does
> this. The ssh completion should perhaps honour the list_types style but

I don't usually have file names ending in those characters either
(someone else whose files I need to copy might have, though) and
one of the reasons I use zsh is that in general it handles even the
corner cases well unlike so many other programs.  Programmers who
think "oh well, no one should put spaces to filenames anyway" and
do not handle the filenames allowed by the relevant standards are
the cause to problems like Y2k.  Of course, in this case zsh is at
the mercy of programs that make it hard to be robust, so it is
understandable if it cannot be done (I guess it would be nice if it
was documented somewhere, however).

-- 
Hannu


      reply	other threads:[~2003-02-17  9:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 13:30 Hannu Koivisto
2003-02-13 14:41 ` Oliver Kiddle
2003-02-13 15:06   ` Hannu Koivisto
2003-02-13 16:12     ` Oliver Kiddle
2003-02-17  9:18       ` Hannu Koivisto [this message]

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=87smunnu35.fsf@lynx.ionific.com \
    --to=azure@iki.fi \
    --cc=okiddle@yahoo.co.uk \
    --cc=zsh-users@sunsite.dk \
    /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).