From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: bug#1212: 23.0.60; split-string-and-unquote problems Date: Thu, 23 Oct 2008 09:55:34 -0400 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1224809229 18475 80.91.229.12 (24 Oct 2008 00:47:09 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 24 Oct 2008 00:47:09 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Oct 24 02:48:10 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 1KtAqY-0002ia-7K for ged-emacs-devel@m.gmane.org; Fri, 24 Oct 2008 02:48:10 +0200 Original-Received: from localhost ([127.0.0.1]:59260 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtApS-0004GG-Kt for ged-emacs-devel@m.gmane.org; Thu, 23 Oct 2008 20:47:02 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KtApG-0004Cs-SJ for emacs-devel@gnu.org; Thu, 23 Oct 2008 20:46:50 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KtApF-0004Bw-Dt for emacs-devel@gnu.org; Thu, 23 Oct 2008 20:46:50 -0400 Original-Received: from [199.232.76.173] (port=60517 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KtApF-0004Bs-6u for emacs-devel@gnu.org; Thu, 23 Oct 2008 20:46:49 -0400 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:34458 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KtApD-0007MJ-6F; Thu, 23 Oct 2008 20:46:47 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjYFAOO3AElFxLrB/2dsb2JhbABFgTHATINOgQs X-IronPort-AV: E=Sophos;i="4.33,473,1220241600"; d="scan'208";a="28798683" Original-Received: from 69-196-186-193.dsl.teksavvy.com (HELO ceviche.home) ([69.196.186.193]) by ironport2-out.teksavvy.com with ESMTP; 23 Oct 2008 20:46:45 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id EAC43B40D1; Thu, 23 Oct 2008 09:55:34 -0400 (EDT) In-Reply-To: (Eli Zaretskii's message of "Thu, 23 Oct 2008 06:29:07 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:104921 Archived-At: >> >> >> 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. >> >> No, they're used to run commands. Without going through a shell. >> > Then why would one need quoting? >> >> Because when you run a command with start-process or call-process, you >> need to specify a list of strings (each being an argument), but the user >> usually wants to enter the list within a single minibuffer. So from the >> string returned by the read-string (or equivalent) function, we need to >> get a list of strings. > If I am prompted for a command in the minibuffer, as in "M-x compile", > I will type a command that uses shell quoting (assuming I need > quoting). That is the natural thing to do, so I expect most users to > do the same. I don't expect many of them to use Lisp string quoting > for commands. Indeed, `compile' uses a shell and hence obeys shell quoting. Stefan