From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Hannu Koivisto <azure@iki.fi>
Cc: zsh-users@sunsite.dk
Subject: Re: Remote scp completion that can handle spaces etc. in pathnames
Date: Thu, 13 Feb 2003 15:41:44 +0100 [thread overview]
Message-ID: <29391.1045147304@finches.logica.co.uk> (raw)
In-Reply-To: <87d6lwqper.fsf@lynx.ionific.com>
On 13 Feb, you wrote:
>
> Let's say that there is a directory "foo bar" on host baz. If I
> try to copy it recursively with scp from baz to the current host, I
> have to say ``scp -r baz:foo\\\ bar .'' That is, I need to
> "double quote". However, if I use zsh's completion to get me that
> directory, i.e. I write ``scp -r baz:fo<tab>'', I get
> ``scp -r baz:foo\ bar/'', which does not work.
>
> I use openssh 3.4p1 and zsh 4.0.4 on Debian GNU/Linux woody. Is
> this handled differently in a later (stable or development) version
> and/or would this be easy to fix locally?
Patch below should fix this. _ssh has changed a bit since 4.0.4 so I'm
not sure how easy it would be to modify for that.
> I also note that pathnames in remote commands are not completed
> remotely, i.e. if I write ``ssh somehost ls f<tab>'', zsh completes
> local filesystem entries beginning with f. I wonder if this could
> be smarter as well.
It could possibly be done by somehow doing a temporary substitution of
_path_files by _remote_files but saving the original _path_files and
doing any other necessary fiddling would be more than a bit messy so I'm
not going to attempt it.
Oliver
Index: Completion/Unix/Command/_ssh
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_ssh,v
retrieving revision 1.18
diff -u -r1.18 _ssh
--- Completion/Unix/Command/_ssh 7 Jan 2003 08:49:16 -0000 1.18
+++ Completion/Unix/Command/_ssh 13 Feb 2003 14:29:21 -0000
@@ -17,9 +17,9 @@
while _tags; do
while _next_label files expl ${suf:-remote directory}; do
[[ -n $suf ]] && compadd "$@" "$expl[@]" -d remdispf \
- ${remdispf%[*=@|]} && ret=0
+ ${(q)remdispf%[*=@|]} && ret=0
compadd ${suf:+-S/} "$@" "$expl[@]" -d remdispd \
- ${remdispd%/} && ret=0
+ ${(q)remdispd%/} && ret=0
done
(( ret )) || return 0
done
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
next prev parent reply other threads:[~2003-02-13 14:39 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 [this message]
2003-02-13 15:06 ` Hannu Koivisto
2003-02-13 16:12 ` Oliver Kiddle
2003-02-17 9:18 ` Hannu Koivisto
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=29391.1045147304@finches.logica.co.uk \
--to=okiddle@yahoo.co.uk \
--cc=azure@iki.fi \
--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).