From: Bart Schaefer <schaefer@brasslantern.com>
To: Alexey Tourbin <at@altlinux.ru>, zsh-workers@sunsite.dk
Subject: Re: zsh-4.2.0-pre-4: problems with _remote_files
Date: Thu, 25 Mar 2004 16:58:14 +0000 [thread overview]
Message-ID: <1040325165814.ZM17555@candle.brasslantern.com> (raw)
In-Reply-To: <20040325102854.GA4785@solemn.turbinal.org>
On Mar 25, 1:28pm, Alexey Tourbin wrote:
}
} I've tracked down the problem: using _call_program requires extra
} quoting because of additional level of indirection inside eval "$argv".
This was already discussed in zsh-workers/19666,19668 and surrounding
thread, and a patch has already been committed to CVS on sourceforge.
next prev parent reply other threads:[~2004-03-25 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 15:07 Alexey Tourbin
2004-03-25 10:28 ` Alexey Tourbin
2004-03-25 16:58 ` Bart Schaefer [this message]
2004-03-25 20:14 ` Alexey Tourbin
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=1040325165814.ZM17555@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=at@altlinux.ru \
--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).