From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: bug#1212: 23.0.60; split-string-and-unquote problems Date: Wed, 22 Oct 2008 21:43:20 +0200 Message-ID: References: Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1224704625 5335 80.91.229.12 (22 Oct 2008 19:43:45 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 22 Oct 2008 19:43:45 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 22 21:44:46 2008 connect(): Connection refused Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KsjdN-0003BB-8O for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2008 21:44:45 +0200 Original-Received: from localhost ([127.0.0.1]:55896 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsjcH-0006xT-MB for ged-emacs-devel@m.gmane.org; Wed, 22 Oct 2008 15:43:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KsjcC-0006so-8R for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:43:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KsjcA-0006np-9J for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:43:31 -0400 Original-Received: from [199.232.76.173] (port=41851 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KsjcA-0006nc-5P for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:43:30 -0400 Original-Received: from mtaout5.012.net.il ([84.95.2.13]:46771) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Ksjc9-000820-GM for emacs-devel@gnu.org; Wed, 22 Oct 2008 15:43:29 -0400 Original-Received: from HOME-C4E4A596F7 ([77.126.98.197]) by i_mtaout5.012.net.il (HyperSendmail v2004.12) with ESMTPA id <0K9500DIEO6JZVE0@i_mtaout5.012.net.il> for emacs-devel@gnu.org; Wed, 22 Oct 2008 21:44:44 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 9.1 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:104857 Archived-At: > From: Stefan Monnier > Cc: emacs-devel@gnu.org > Date: Wed, 22 Oct 2008 10:58:49 -0400 > > >> The list of strings will be passed to call-process or start-process > >> which ultimately will pass them to execv or somesuch: no shell in sight. > > But the original string could have been a properly quoted shell > > command, and those do use sh-style quoting. > > I do not understand: what makes you think it could be a properly quoted > shell command? Because you said that working with shell commands was why these functions were invented in the first place. And that is how they are used in Emacs as of now. > /We/ define what it can accept. But hopefully, /we/ decide that to accomplish some specific practical goal, not just to craft a function that accepts a small subset of that goal. Right? So what class of _practical_ problems do these two functions solve? After all, using Lisp syntax in shell commands is not an interesting use-case, is it? > And as of now, we (well, admittedly, > IIUC, it's mostly just myself) decided that it accepts a syntax derived > from Elisp string quoting, so if you feed it sh-style quoted strings, it > won't work in general (tho it will if you stick to the common subset, of > course). Are you saying that modes that work with shell commands, such as GUD, should not use these functions, because they don't generally support the full syntax of quoted shell commands?