From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Christopher Howard Newsgroups: gmane.emacs.devel Subject: eshell !foo expansion Date: Wed, 09 Oct 2024 09:46:51 -0800 Message-ID: <87msjdp3sk.fsf@librehacker.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="14692"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Jim Porter To: Emacs Devel Mailing List Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 09 19:48:39 2024 Return-path: Envelope-to: ged-emacs-devel@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 1syane-0003TT-Uo for ged-emacs-devel@m.gmane-mx.org; Wed, 09 Oct 2024 19:48:38 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1syamR-0005Xs-7F; Wed, 09 Oct 2024 13:47:23 -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 1syamI-0005Wc-N3 for emacs-devel@gnu.org; Wed, 09 Oct 2024 13:47:15 -0400 Original-Received: from mx.kolabnow.com ([212.103.80.155]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1syamG-0003KJ-3b for emacs-devel@gnu.org; Wed, 09 Oct 2024 13:47:14 -0400 Original-Received: from localhost (unknown [127.0.0.1]) by mx.kolabnow.com (Postfix) with ESMTP id A9EAC34F423F; Wed, 9 Oct 2024 19:47:08 +0200 (CEST) Authentication-Results: ext-mx-out011.mykolab.com (amavis); dkim=pass (2048-bit key) reason="pass (just generated, assumed good)" header.d=kolabnow.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kolabnow.com; h= content-transfer-encoding:content-type:content-type:mime-version :message-id:date:date:subject:subject:from:from:received :received:received; s=dkim20240523; t=1728496025; x=1730310426; bh=oG/iP4TgTvUrM9KLN2baP/hpnn6LHcP/Yh41uppgB4g=; b=pwL5Ve0CEObD EAt4da7K3c2wDrFZ5aVKvKSoFa7RWzIhM6QYcSse4kS6tQheyAABUTQBpXhmzls1 NbfoICHRmK53TUgvpArml3Uf/oxfHtKvluXzClRfxpGlwQkURIX3hB+Lt5m22RLv wZm4nUIhZpRUAILIsf9kNEzm62AhnTKYjRBdR0bcvsYDFb0qD4sDQXeHi+tEux2f l4s6EU9zaQyaV/ZxOH8Bpjgtv29MT5Vs4YfR74R3U7LgdXBKQkgxN/8i/k/M7m11 RqflgTpN3aREp2Yl8GCMZIdMpbYf7X0TXSI+LRsekBJt6bu4LnwhDQYpu6+uq/qY mJr3rpT+wg== X-Virus-Scanned: amavis at mykolab.com Original-Received: from mx.kolabnow.com ([127.0.0.1]) by localhost (ext-mx-out011.mykolab.com [127.0.0.1]) (amavis, port 10024) with ESMTP id eqo0TNqpSDeI; Wed, 9 Oct 2024 19:47:05 +0200 (CEST) Original-Received: from int-mx009.mykolab.com (unknown [10.9.13.9]) by mx.kolabnow.com (Postfix) with ESMTPS id 397F634F423E; Wed, 9 Oct 2024 19:47:05 +0200 (CEST) Original-Received: from ext-subm010.mykolab.com (unknown [10.9.6.10]) by int-mx009.mykolab.com (Postfix) with ESMTPS id 017A12094EC1; Wed, 9 Oct 2024 19:47:04 +0200 (CEST) Received-SPF: none client-ip=212.103.80.155; envelope-from=christopher@librehacker.com; helo=mx.kolabnow.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:324452 Archived-At: Hi, I've been combing through the Emacs 30 Eshell manual, as I find the tim= e. I like the !foo expansion syntax, which is very handy. However, I was wo= ndering if there could be some function and keystroke added to expand the t= oken immediately, so you could see the expansion before actually submitting= the entire line to eshell. You might want to do this if, say, you weren't = 100% sure that you are really calling up the desired history command, or pe= rhaps you just want to make a slight tweak to the recalled command before r= unning it. The natural keystroke would be TAB, but that would conflict with preview co= mplete, which is happening at the same time, so I'm not sure what would be = best. Maybe just an interactive function would be enough. --=20 =F0=9F=93=9B Christopher Howard =F0=9F=9A=80 gemini://gem.librehacker.com =F0=9F=8C=90 http://gem.librehacker.com =D7=91=D7=A8=D7=90=D7=A9=D7=99=D7=AA =D7=91=D7=A8=D7=90 =D7=90=D7=9C=D7=94= =D7=99=D7=9D =D7=90=D7=AA =D7=94=D7=A9=D7=9E=D7=99=D7=9D =D7=95=D7=90=D7=AA= =D7=94=D7=90=D7=A8=D7=A5