From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Proposing elisp-eval-target for eval-last-sexp and related commands Date: Sat, 21 Aug 2021 10:37:24 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="7563"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Psionic K Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 21 16:38:37 2021 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 1mHS8p-0001nc-I1 for ged-emacs-devel@m.gmane-mx.org; Sat, 21 Aug 2021 16:38:35 +0200 Original-Received: from localhost ([::1]:49158 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mHS8n-0008JB-QW for ged-emacs-devel@m.gmane-mx.org; Sat, 21 Aug 2021 10:38:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41630) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mHS7o-0007dF-Vu for emacs-devel@gnu.org; Sat, 21 Aug 2021 10:37:33 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:9732) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mHS7l-0007Pu-OR for emacs-devel@gnu.org; Sat, 21 Aug 2021 10:37:31 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 875DA440F5D; Sat, 21 Aug 2021 10:37:27 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4B459440220; Sat, 21 Aug 2021 10:37:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1629556646; bh=FvfuA5lq5MfjVXlTGOQYIqiVzX0LMI4fugx7WPsjtFs=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=OVblhZGtt7qjNudxNB4HiN39l6sTaSv05N1DDkRfLizTL7a+2aBHTiZ9ur4A7WzXY 7TKTC95Q3mO6cx+uLjPDqQd6AfHmCQbzZmoKmQV/RcRIJRqwbE1efxNChFlTDv1Yi6 1k+gsOTWHzRoOv1+EMlBnhPmvdZgH9dsqBrXWsJmNiYykoYfOHqWxcDT2zrPd1It7E CY05ku6CPzMx4DtI0TTYDJHh/s9pPf4z1dYj0WD0g48R8wxrVIvct4ZreHzmwuBBuf 7cgjoEtxqPpd76kN8LwpW5f1RAPUhNsHj+12cjBDHHTxw2xy9TEdEQM31qVhv4CJWF kAkdJNBUqzyEA== Original-Received: from milanesa (24-54-5-63.resi.cgocable.ca [24.54.5.63]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id F1704120376; Sat, 21 Aug 2021 10:37:25 -0400 (EDT) In-Reply-To: (Psionic K.'s message of "Wed, 18 Aug 2021 13:19:42 +0800") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:272792 Archived-At: > Indeed ielm is my workflow for this use case. When I shared a shortcut on > Reddit for the `ielm-change-working-buffer` solution, it was obvious that > many users have a strong preference for working in an elisp major mode > buffer. I can't provide a shortcut however because the `eval-last-sexp` > style functions don't have any `working-buffer` concept like the ielm > implementation. The change I'm proposing will allow the extremely low > friction of the ielm solution but with the freedom of an elisp major mode > buffer. I see. I don't use `eval-last-sexp` often enough to have a clear idea of what the impact of that patch would be in practice, so I'll let others judge. Stefan