zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: Jay Berkenbilt <ejb@ql.org>
Cc: zsh-workers@sunsite.dk, 243385@bugs.debian.org
Subject: Re: [ejb@ql.org: Bug#243385: zsh: rsync completion expands * too soon]
Date: Mon, 12 Apr 2004 22:19:31 -0400	[thread overview]
Message-ID: <20040413021931.GA10355@scowler.net> (raw)
In-Reply-To: <200404130137.i3D1b5CW004764@soup.in.ql.org>

> Yes.  Well, kind of.  It's an eval issue.  The call to _call_program
> (which I have removed) causes the wildcard to be expanded too early
> because it calls eval.  Here's a trace excerpt.

I haven't tried this at all, but maybe this will fix your problem.

Index: Completion/Unix/Command/_rsync
===================================================================
RCS file: /cvsroot/zsh/zsh/Completion/Unix/Command/_rsync,v
retrieving revision 1.8
diff -u -r1.8 _rsync
--- Completion/Unix/Command/_rsync	14 Nov 2003 11:56:55 -0000	1.8
+++ Completion/Unix/Command/_rsync	13 Apr 2004 02:05:03 -0000
@@ -37,8 +37,8 @@
 
   if zstyle -T ":completion:${curcontext}:" remote-access; then
     slash=/
-    remfiles=(${(f)"$(_call_program files ssh -a -x ${words[CURRENT]%:*} ls -d1F ${${${words[CURRENT
-]#*:}:h}/${slash}(#e)/}/\* 2>/dev/null)"})
+    remfiles=(${(f)"$(_call_program files ssh -a -x ${words[CURRENT]%:*} ls -d1F "${${${words[CURRENT
+]#*:}:h}/${slash}(#e)/}/\* 2>/dev/null")"})
 
     remdispf=(${remfiles:#*/})
     remdispd=(${(M)remfiles:#*/})


  reply	other threads:[~2004-04-13  2:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13  1:21 Clint Adams
2004-04-13  1:37 ` Jay Berkenbilt
2004-04-13  2:19   ` Clint Adams [this message]
2004-04-13 16:17     ` Jay Berkenbilt
2004-04-13 17:44       ` Bart Schaefer
2004-04-13 22:55         ` Clint Adams
2004-04-14 16:37           ` more boring zsh-in-Arch chatter [was Re: [ejb@ql.org: Bug#243385: zsh: rsync completion expands * too soon]] Clint Adams
2004-04-25  2:07             ` more boring zsh-in-Arch chatter Clint Adams

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=20040413021931.GA10355@scowler.net \
    --to=clint@zsh.org \
    --cc=243385@bugs.debian.org \
    --cc=ejb@ql.org \
    --cc=zsh-workers@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).