From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.bugs Subject: bug#46351: 28.0.50; Add convenient way to bypass Eshell's own pipelining Date: Mon, 24 Jan 2022 18:39:15 -0800 Message-ID: <639b931e-7816-ef07-510c-71178ff19fff@gmail.com> References: <8735lersah.fsf@melete.silentflame.com> <87pmohrzcj.fsf@gmx.de> <87zgnkj2me.fsf@melete.silentflame.com> <87fspc276n.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39014"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 46351@debbugs.gnu.org, Robert Pluim , Michael Albinus To: Lars Ingebrigtsen , Sean Whitton Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 25 03:41:39 2022 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 1nCBm7-0009zx-ID for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 25 Jan 2022 03:41:39 +0100 Original-Received: from localhost ([::1]:58436 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nCBm6-0004bk-0g for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 24 Jan 2022 21:41:38 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:39546) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nCBkZ-0004bT-02 for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 21:40:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53549) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nCBkY-0002wT-GP for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 21:40:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nCBkY-0007MC-05 for bug-gnu-emacs@gnu.org; Mon, 24 Jan 2022 21:40:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Jim Porter Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 25 Jan 2022 02:40:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 46351 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 46351-submit@debbugs.gnu.org id=B46351.164307836428226 (code B ref 46351); Tue, 25 Jan 2022 02:40:01 +0000 Original-Received: (at 46351) by debbugs.gnu.org; 25 Jan 2022 02:39:24 +0000 Original-Received: from localhost ([127.0.0.1]:46452 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nCBjv-0007LB-PC for submit@debbugs.gnu.org; Mon, 24 Jan 2022 21:39:23 -0500 Original-Received: from mail-pg1-f174.google.com ([209.85.215.174]:37500) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nCBjt-0007Kx-W3 for 46351@debbugs.gnu.org; Mon, 24 Jan 2022 21:39:22 -0500 Original-Received: by mail-pg1-f174.google.com with SMTP id e16so7791308pgn.4 for <46351@debbugs.gnu.org>; Mon, 24 Jan 2022 18:39:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=MGUTUIOFkaJGHORQ4yH+vPr3f+ojEerB2uxYXAC6RWI=; b=ZjQE2hzfWykGO4OWG6mbcQymj8t7MSik0I0ZXHkfFQe7XK2cT5qts+ABHQh/PY7dqF bKlqi6yWx9zpWUEhvTYHwGM/6g42LaC16tBA8myt4FT3c/fL2lyQyPnweNgib7n3IeMi YyD/ik717EDqjaGBCEBZVuMLUioXMGD20XqPxQ04lKOvBSLBUS9GIHs9cGvIq/tP+YPg Y60evNpbRvTaZDDp6sjqrd/Q8QdHbZKuGjGGjxBbRkf//UXGxVElraBoR9KyE0I/DizM 3s2oKO7cf2bFHfBvBU09cshHhcuCuQiP4HaZz3kxYReYtA3vRYxNZGCLvd6+6H1ckVpg kS/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=MGUTUIOFkaJGHORQ4yH+vPr3f+ojEerB2uxYXAC6RWI=; b=FZjuFajg2Tg0bkhepxis+oo4Db7odu3OgwQ6A3YpSjTjB0/G7WAvh6fAVqZXj5tn18 3laht6NOU4PIeGlQcoYFJQcBFJPQ5pkKfT9DJpi70f4eTxUntcBpVuJjV/u+CT79RuFh +FlcUwc5wCxvLdbacL+51pCj8jFm+9YosWvTiBS+EUSAbQP7Ss8D6HZY208+QoYFyMxd Cd6lIanXsIDerm8f71Om/HgWBHdoKzfMayod6HrL6QDewAkkgepm74eY1qkxNhdnln4V KO36pUs7idlhj+1J6jDYr/cQ/sookP3YGZwdAo5mrcGgn3wEOiWosNiRBj2QIorTtQww Fh1A== X-Gm-Message-State: AOAM530SLLeYM07+Z6VN6dzxFDAvOqkqshyu3YNn+5go2PgtGEY9u9nJ aoWTn7nCHWAVR29igmydVJg= X-Google-Smtp-Source: ABdhPJwHr4hMNX0g6W7tPbTUxdf1yLTERf4KwVsBq+Uw/9v36zozMn21lpXxPUmHhzKDmUAUo1LtbQ== X-Received: by 2002:a65:6a97:: with SMTP id q23mr14077442pgu.464.1643078356134; Mon, 24 Jan 2022 18:39:16 -0800 (PST) Original-Received: from [192.168.1.2] (cpe-76-168-148-233.socal.res.rr.com. [76.168.148.233]) by smtp.googlemail.com with ESMTPSA id r11sm18015097pff.81.2022.01.24.18.39.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 24 Jan 2022 18:39:15 -0800 (PST) In-Reply-To: <87fspc276n.fsf@gnus.org> Content-Language: en-US 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" Xref: news.gmane.io gmane.emacs.bugs:225141 Archived-At: On 1/24/2022 12:46 PM, Lars Ingebrigtsen wrote: > Sean Whitton writes: > >> Likewise fixed in the attached. > > Thanks; pushed to Emacs 29. I just noticed a small bit of breakage with this. It's no longer possible to refer to Lisp functions in Eshell like so: #'upcase Eshell explicitly supports this construct (see `eshell-lisp-regexp'), though it doesn't appear to be documented in the manual. Currently, this syntax is only occasionally useful, but I'm working on a patch series where it'll likely become a lot more common. My patches will add support for piping to Lisp functions, so that you can do the following, for example: $ echo hi | #'upcase HI It looks like the breakage in parsing #'upcase is the result of `eshell-parse-external-pipeline' trying to skip over args like '*|' (with the quotes). However, it sees the single-quote in #'upcase and then calls `eshell-parse-literal-quote', resulting in the error message: Expecting completion of delimiter ' ...