|
From: | Paul Eggert |
Subject: | Re: [PATCH] Add shell-quasiquote. |
Date: | Tue, 20 Oct 2015 09:21:56 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Taylan Ulrich Bayırlı/Kammer wrote:
(shell-command (shqq (./foo bar baz))) /bin/bash: ./foo: No such file or directory I don't see a problem.
Nor do I. And you can use the same technique to run "./break" or "/bin/break", should anyone be crazy enough to create a file with either name. The point is that shqq's quoting mechanism doesn't work any better than shell-quote-argument does for contrived examples like "break".
I will use shell-quote-argument once the real problem with it is fixed.
No case has been presented that there's a significant problem with it. The argument that one might want to run an executable named "if" is, as you say, a trivial one, i.e., not significant.
Yes, there are problems if you use shell-quote-argument with weird shells that don't use standard quoting conventions, but that's also true for shqq's or for any other quoting function, so it's not a knock on shell-quote-argument's implementation.
[Prev in Thread] | Current Thread | [Next in Thread] |