From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Random832 Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Add shell-quasiquote. Date: Sun, 18 Oct 2015 15:17:53 -0400 Message-ID: <8737x87zq6.fsf@fastmail.com> References: <87si59wj42.fsf@T420.taylan> <83eggt4esi.fsf@gnu.org> <87fv19wh7b.fsf@T420.taylan> <83bnbx4d7e.fsf@gnu.org> <87twppuzfu.fsf@T420.taylan> <83a8rh48if.fsf@gnu.org> <87io65utmt.fsf@T420.taylan> <5622B337.4050700@yandex.ru> <876125uqzw.fsf@T420.taylan> <5622BE84.8030209@yandex.ru> <87twpptato.fsf@T420.taylan> <87pp0cehly.fsf@gmx.de> <878u70trqz.fsf@T420.taylan> <87si58phte.fsf@gmx.de> <87io648h8r.fsf@fastmail.com> <83oafwhykw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1445196025 9962 80.91.229.3 (18 Oct 2015 19:20:25 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 18 Oct 2015 19:20:25 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Oct 18 21:20:07 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZntV1-00010U-2N for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2015 21:20:07 +0200 Original-Received: from localhost ([::1]:35269 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZntTe-0005nn-Pa for ged-emacs-devel@m.gmane.org; Sun, 18 Oct 2015 15:18:42 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45242) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZntTR-0005ni-1Z for emacs-devel@gnu.org; Sun, 18 Oct 2015 15:18:29 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZntTN-0001WK-P2 for emacs-devel@gnu.org; Sun, 18 Oct 2015 15:18:28 -0400 Original-Received: from plane.gmane.org ([80.91.229.3]:58100) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZntTN-0001WF-IB for emacs-devel@gnu.org; Sun, 18 Oct 2015 15:18:25 -0400 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZntTL-0007lZ-F5 for emacs-devel@gnu.org; Sun, 18 Oct 2015 21:18:23 +0200 Original-Received: from c-68-39-146-59.hsd1.in.comcast.net ([68.39.146.59]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Oct 2015 21:18:23 +0200 Original-Received: from random832 by c-68-39-146-59.hsd1.in.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 18 Oct 2015 21:18:23 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 30 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-68-39-146-59.hsd1.in.comcast.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:HPZsjXMOhVT/H+JuiJ0gYiOscSw= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:192006 Archived-At: Eli Zaretskii writes: >> From: Random832 >> what is an unusual shell > > Any shell that is not the "system's standard shell" is unusual. I > thought the text made that clear; if not, please suggest how to > clarify it (without having an exhaustive list of shells, which would > be a maintenance burden). It works on shells that share quoting rules with POSIX, and it works on MS-DOS, and it works on MS Windows with the assumption that cmdproxy or any shell listed in w32-system-shells uses the same rules as cmd.exe and that any other shell uses POSIX semantics. This gives people a good starting point for understanding what is "unusual" and what is not, (i.e. bash, ksh, and zsh are not unusual, even if they are not the system shell) without requiring an exhaustive list. >> And I know there's nothing to be done for it, but the fact that it >> does not have any way to escape wildcards is concerning. > > Sorry, I don't follow: in what situation do you think the wildcards > cannot be escaped? Are you still talking about MS-Windows? Yes, sorry. A typical Windows program (at least, one compiled with MSVC's setargv.obj) will try to interpret wildcards in any part of CommandLineToArgv's result which contains a ? or * character, with no provision to prevent it from doing so. (In particular, double quotes have no effect).