From: "Ignacy Gawędzki" <zsh@qult.net>
To: zsh-workers@zsh.org
Subject: File completion of scp (tentative fix)
Date: Wed, 23 Nov 2011 01:21:50 +0100 [thread overview]
Message-ID: <20111123002149.GA9025@zenon.in.qult.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
Hi,
It's been some time since I wanted to track this bug down and finally took the
time to do it.
Supposing you have a remote host with a file in the home directory that begins
with a dash, the completion may fail because the file argument is interpreted
by ls as an option.
See the attached patch, which adds a -- before the pattern, so that files
starting with a dash won't possibly be considered as options. This is the way
to go with a GNU ls on the other side, but I don't know how other versions
will interpret that. Maybe something more sophisticated has to be done to
remain as generic as possible.
--
Save the whales. Feed the hungry. Free the mallocs.
[-- Attachment #2: zsh-scp-completion.patch --]
[-- Type: text/x-diff, Size: 657 bytes --]
diff --git a/Completion/Unix/Command/_ssh b/Completion/Unix/Command/_ssh
index d0944c6..0ec9c84 100644
--- a/Completion/Unix/Command/_ssh
+++ b/Completion/Unix/Command/_ssh
@@ -16,7 +16,7 @@ _remote_files () {
then rempat="${PREFIX%%[^./][^/]#}\*"
else rempat="${(q)PREFIX%%[^./][^/]#}\*"
fi
- remfiles=(${(M)${(f)"$(_call_program files ssh -o BatchMode=yes $args -a -x ${IPREFIX%:} ls -d1FL "$rempat" 2>/dev/null)"}%%[^/]#(|/)})
+ remfiles=(${(M)${(f)"$(_call_program files ssh -o BatchMode=yes $args -a -x ${IPREFIX%:} ls -d1FL -- "$rempat" 2>/dev/null)"}%%[^/]#(|/)})
compset -P '*/'
compset -S '/*' || suf='remote file'
next reply other threads:[~2011-11-23 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 0:21 Ignacy Gawędzki [this message]
2011-11-23 9:49 ` Antwort: " Andreas Pistoor
2011-11-23 9:52 ` 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=20111123002149.GA9025@zenon.in.qult.net \
--to=zsh@qult.net \
--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).