From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: sbaugh@catern.com Newsgroups: gmane.emacs.bugs Subject: bug#65902: 29.0.92; emacsclient-mail.desktop fails due to complicated escaping Date: Wed, 13 Sep 2023 13:01:51 +0000 (UTC) Message-ID: <87msxqtef4.fsf@catern.com> References: <871qf2vmi4.fsf@catern.com> <87v8ceu7o0.fsf@catern.com> <83fs3int3t.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8907"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 65902@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 13 15:03:20 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qgPWZ-000202-Ch for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 13 Sep 2023 15:03:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qgPWF-0000dP-Ih; Wed, 13 Sep 2023 09:02:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qgPWE-0000X4-1k for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 09:02:58 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qgPWD-0006Hq-P1 for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 09:02:57 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qgPWI-0001mf-8y for bug-gnu-emacs@gnu.org; Wed, 13 Sep 2023 09:03:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: sbaugh@catern.com Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 13 Sep 2023 13:03:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 65902 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 65902-submit@debbugs.gnu.org id=B65902.16946101256791 (code B ref 65902); Wed, 13 Sep 2023 13:03:02 +0000 Original-Received: (at 65902) by debbugs.gnu.org; 13 Sep 2023 13:02:05 +0000 Original-Received: from localhost ([127.0.0.1]:32897 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qgPVM-0001lR-Mu for submit@debbugs.gnu.org; Wed, 13 Sep 2023 09:02:05 -0400 Original-Received: from s.wrqvtzvf.outbound-mail.sendgrid.net ([149.72.126.143]:7066) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qgPVK-0001ku-VW for 65902@debbugs.gnu.org; Wed, 13 Sep 2023 09:02:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=catern.com; h=from:subject:in-reply-to:references:mime-version:to:cc:content-type: content-transfer-encoding:cc:content-type:from:subject:to; s=s1; bh=d/XQXB+zyoK5543jLJsjJXhpkelj1D3ArYEOINcbAGw=; b=HwgDXbm0mY3jVJUUarAUSZiMB1StmlzY8bQ+w4jKUObvD+R7z+OYMB6HgAM/UIt6ZJjj EBfBxhLc+P1VbHIK/W737BGwImBSjZ73C4tN/yIQ9xy2Rqtq67pz3+mhiiHsCojUEopnmp yws4haPMLfnSBVrVMHtOx0kdHT5b0mK15sJudHNrI/5W1PTa91j/jPsTwVJkKC0TfiiB2P ldJja1miSP8hShlzvlATtNwUAnJBL+69Hkda+ll7Vc0WZ0SqR1NtuI/Tka4VLGlyO0YFk9 DydJ/FUDtU/zxmqRKPRzgQArF+0jbUUHEcsBQnifoVdCX2l+vnbPGJfq5ZIHSdnA== Original-Received: by filterdrecv-7765c6879f-kht5h with SMTP id filterdrecv-7765c6879f-kht5h-1-6501B2BF-13B 2023-09-13 13:01:51.817695253 +0000 UTC m=+2930786.635545343 Original-Received: from earth.catern.com (unknown) by geopod-ismtpd-18 (SG) with ESMTP id EtcvEPjlRyCQg-W_NcUgQw Wed, 13 Sep 2023 13:01:51.631 +0000 (UTC) X-Comment: SPF check N/A for local connections - client-ip=::1; helo=localhost; envelope-from=sbaugh@catern.com; receiver=gnu.org Original-Received: from localhost (localhost [IPv6:::1]) by earth.catern.com (Postfix) with ESMTPSA id 5F4CE62523; Wed, 13 Sep 2023 09:01:51 -0400 (EDT) In-Reply-To: <83fs3int3t.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 13 Sep 2023 15:41:10 +0300") X-SG-EID: ZgbRq7gjGrt0q/Pjvxk7wM0yQFRdOkTJAtEbkjCkHbJsDIxVZAS6ctWFFVNKgHSRQCZlJ0D1/8rM68qQhH0y14yTwRW3Q9XwioRuLdGLnCq0vagagt31A3AVRTqxqQImWdimgqLKQWLiN4UE3qCy64KoRDUxU42QT9FZ/L1FpreXTAolHPqeb+V4RejUfPjv0LqBJa6CRmxoA2Huyu/CCQ== X-Entity-ID: d/0VcHixlS0t7iB1YKCv4Q== X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:270272 Archived-At: Eli Zaretskii writes: >> From: sbaugh@catern.com >> Date: Wed, 13 Sep 2023 02:30:08 +0000 (UTC) >> >> This patch avoids the complicated scripting needed for >> emacsclient-mail.desktop by adding a new flag to emacsclient, --funcall, >> which mirrors emacs --funcall and allows emacsclient-mail.desktop to be >> basically the same as emacs-mail.desktop. >> >> I expect this to also be useful in other places; the need to escape >> arbitrary inputs before passing them to emacsclient is frequently >> annoying. > > Is quoting the only issue with --eval? If so, why not have a variant > of --eval that quotes the argument by itself, like you do in the > patch, i.e. by using quote_argument, instead of inventing yet another > weird option with its own small DSL and extra-special rules of how to > write the command line with it? I am not sure what you're suggesting. Can you show how the equivalent of: emacsclient --apply message-mailto -- %u would work with that design? > More generally, I cannot say I'm happy that we basically are > reiterating everything that was said in bug#57752 instead of picking > up where it left off. Why is it useful to have another discussion > like that one (which will probably end up at the same impasse)? I admit I didn't see that bug until now, but the way in which this is different is that I have now read the discussion, incorporated all the advice, and I'm actually implementing it :) Probably these bugs could/should be merged though.