From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: taylanbayirli@gmail.com (Taylan Ulrich =?utf-8?Q?Bay=C4=B1rl=C4=B1?= =?utf-8?Q?=2FKammer?=) Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Add shell-quasiquote. Date: Tue, 20 Oct 2015 09:41:26 +0200 Message-ID: <878u6ykmvt.fsf@T420.taylan> References: <87si59wj42.fsf@T420.taylan> <878u6znii9.fsf@T420.taylan> <877fmjj9p6.fsf@fencepost.gnu.org> <87zizfm2dq.fsf@T420.taylan> <871tcr7yvq.fsf@fastmail.com> <87mvvfm0bd.fsf@T420.taylan> <56250803.5080601@cs.ucla.edu> <87a8ren5ys.fsf@T420.taylan> <56259BB1.3070908@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1445326904 17661 80.91.229.3 (20 Oct 2015 07:41:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 20 Oct 2015 07:41:44 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 20 09:41:43 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 1ZoRY6-0005Tk-Er for ged-emacs-devel@m.gmane.org; Tue, 20 Oct 2015 09:41:34 +0200 Original-Received: from localhost ([::1]:44333 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoRY5-00086Z-0E for ged-emacs-devel@m.gmane.org; Tue, 20 Oct 2015 03:41:33 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58553) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoRY1-00086U-Ql for emacs-devel@gnu.org; Tue, 20 Oct 2015 03:41:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZoRY0-0005At-PR for emacs-devel@gnu.org; Tue, 20 Oct 2015 03:41:29 -0400 Original-Received: from mail-wi0-x233.google.com ([2a00:1450:400c:c05::233]:36160) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZoRY0-0005Ag-JW for emacs-devel@gnu.org; Tue, 20 Oct 2015 03:41:28 -0400 Original-Received: by wicfx6 with SMTP id fx6so32108656wic.1 for ; Tue, 20 Oct 2015 00:41:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type:content-transfer-encoding; bh=oVxJS8EhIoB8RZS51z69A8mB8+lfoare9dbAAvP5RJE=; b=G5fNwp06yHFCOw0fsyw43nPL3RYb9Ejip9dvusxxVgG3CRV2pW7WS/EhC+v/8Sop3q vUUVOaLwEgurT/hsuwFFgaNszZvjDLJuGFe/qFYQGWyiemarQ4IvIafLv0xl+LkudNoo bA1kEa2CRkxfyDVqR4IGlnMe9CtQD47nL0pD6YTPcCi8H8EAwCFQXWt211Zd7B6XDPGN AlgJo4YtgmGuAhjmSgeyq1BxK04fwIGaZS1Yc7ldNU8nxxR+Z+YZ6dkTOTNK8fhkehOm F3qsB9iVB7Pfa+RqUSPH6IwdrjBborSRzAbkMDGzO6m7Ch/xK1wKzjk7icpG5lYZdgmy U6MA== X-Received: by 10.180.11.37 with SMTP id n5mr2545185wib.20.1445326888026; Tue, 20 Oct 2015 00:41:28 -0700 (PDT) Original-Received: from T420.taylan ([2a02:908:c32:4740:221:ccff:fe66:68f0]) by smtp.gmail.com with ESMTPSA id w1sm2045552wjz.37.2015.10.20.00.41.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Oct 2015 00:41:27 -0700 (PDT) In-Reply-To: <56259BB1.3070908@cs.ucla.edu> (Paul Eggert's message of "Mon, 19 Oct 2015 18:41:05 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c05::233 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:192158 Archived-At: Paul Eggert writes: > Taylan Ulrich Bay=C4=B1rl=C4=B1/Kammer wrote: > >> Who ever talked about running files in the current directory? > > It's normal to run files in the current directory. Any function that > wants to run arbitrary shell commands needs to be able to do > that. Concerns were raised about not being able to run arbitrary > commands, so the topic is relevant. > >> the shell does not try to run the . file as a script, no matter what >> PATH is. > > No, the shell command ". ." tries to run the . file as a script, > assuming that PATH starts with ".:". > >> How is PATH even relevant to the topic?) > > PATH can be relevant if a shell command name lacks slashes. > > Admittedly it's weird to try to run "." as a shell script, but what > can I say? This thread already went down that rabbit hole when the > idea of running a command named "if" was raised. And "." is not a > unique case here; for example, shqq won't run an executable named > "break" either. (shell-command (shqq (./foo bar baz))) /bin/bash: ./foo: No such file or directory I don't see a problem. (In real code, I would use the string "./foo" instead because I feel uneasy relying on ./foo being a valid symbol.) I said (shqq (if ...)) will try to call e.g. /bin/if. I said that this is maybe slightly more useful and consistent. I believe I was fairly clear in the implication that this is a trivial matter, and pointed out explicitly that I will use shell-quote-argument once the real problem with it is fixed. I never said that any (shqq (x ...)) will try to look up x in PATH no matter what x is, or any other things you seem to have taken from what I said. Apologies if my previous answer was too hasty or unclear, but please understand that I'm already very irritated because of the non-resolution of the bug report despite providing a patch solving the exact problem, and because of the continued unwillingness to accept the code refusing to use shell-quote-argument despite that the reasons for refusing to use it were explained in detail. Taylan