From: Jay Berkenbilt <ejb@ql.org>
To: clint@zsh.org
Cc: zsh-workers@sunsite.dk, 243385-forwarded@bugs.debian.org
Subject: Re: [ejb@ql.org: Bug#243385: zsh: rsync completion expands * too soon]
Date: Mon, 12 Apr 2004 21:37:05 -0400 [thread overview]
Message-ID: <200404130137.i3D1b5CW004764@soup.in.ql.org> (raw)
In-Reply-To: <20040413012117.GA9729@scowler.net> (clint@zsh.org)
> I assume that this is a quoting issue again.
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.
+_rsync_remote_files:37> remfiles=+_rsync_remote_files:1> _call_program files ssh -a -x apex ls -d1F '/*'
+_call_program:3> local tmp
+_call_program:5> zstyle -s :completion::complete:rsync:argument-rest:files command tmp
+_call_program:12> eval 'ssh -a -x apex ls -d1F /*'
+(eval):1> ssh -a -x apex ls -d1F /bin /boot /cdrom /cdrom0 /dark /dark2 /dev /etc /fc1 /floppy /home /initrd /initrd.img /initrd.img.old /lib /mnt /opt /proc /projects /.rnd /root /sbin /smb /sys /systems /tmp /tmp-Xhack /u1 /u2 /usr /var /vmlinuz
+_rsync_remote_files:37> remfiles=( /bin/ /boot/ /dev/ /etc/ /home@ /initrd/ /lib/ /mnt/ /opt/ /proc/ /projects@ /root/ /sbin/ /smb/ /systems/ /tmp/ /usr/ /var/ )
The ls command ("(eval:1)" above) does an ls on the remote system
after having expanded the wildcard on my local system.
--Jay
next prev parent reply other threads:[~2004-04-13 1:52 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 [this message]
2004-04-13 2:19 ` Clint Adams
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=200404130137.i3D1b5CW004764@soup.in.ql.org \
--to=ejb@ql.org \
--cc=243385-forwarded@bugs.debian.org \
--cc=clint@zsh.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).