From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: "whether the global keymap C-x 4 will be replaced by a command," Date: Fri, 17 Jul 2020 01:57:57 +0300 Organization: LINKOV.NET Message-ID: <87blkfqd8q.fsf@mail.linkov.net> References: <83ft9woo68.fsf@gnu.org> <87wo377wxp.fsf_-_@mail.linkov.net> <83ft9um9op.fsf@gnu.org> <838sfmm54o.fsf@gnu.org> <87y2nkbah5.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="391"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: Eli Zaretskii , rms@gnu.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 17 01:28:51 2020 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 1jwDJ5-000AZv-5g for ged-emacs-devel@m.gmane-mx.org; Fri, 17 Jul 2020 01:28:51 +0200 Original-Received: from localhost ([::1]:39752 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jwDJ4-0003iN-3g for ged-emacs-devel@m.gmane-mx.org; Thu, 16 Jul 2020 19:28:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51808) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jwDII-0002u2-W1 for emacs-devel@gnu.org; Thu, 16 Jul 2020 19:28:03 -0400 Original-Received: from relay10.mail.gandi.net ([217.70.178.230]:57813) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jwDIG-0005o6-MS; Thu, 16 Jul 2020 19:28:02 -0400 Original-Received: from mail.gandi.net (m91-129-103-18.cust.tele2.ee [91.129.103.18]) (Authenticated sender: juri@linkov.net) by relay10.mail.gandi.net (Postfix) with ESMTPSA id DEECC240003; Thu, 16 Jul 2020 23:27:54 +0000 (UTC) In-Reply-To: (Stefan Monnier's message of "Thu, 16 Jul 2020 00:07:25 -0400") Received-SPF: pass client-ip=217.70.178.230; envelope-from=juri@linkov.net; helo=relay10.mail.gandi.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/07/16 19:27:56 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -35 X-Spam_score: -3.6 X-Spam_bar: --- X-Spam_report: (-3.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-1, 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:252992 Archived-At: >> Then it could bind `overriding-terminal-local-map` (instead of using >> `set-transient-map`) > > Not sure what's the difference. It could simplify implementation of commands that need to modify more variables, e.g. both `overriding-terminal-local-map` and `display-buffer-overriding-action`. >> and also bind `display-buffer-overriding-action` >> (instead of using `display-buffer-override-next-command`). > > Neither do I understand what's better about "bind > `display-buffer-overriding-action`" compared to using > `display-buffer-override-next-command`. For simplicity as well. And for uniformity of modifying the environment of the next command the same way for different variables. >> This will also solve the problem of setting `default-directory` >> for `C-x p p` (project-switch-project). As explained in >> https://debbugs.gnu.org/41890#196 >> currently it's not possible to bind the value of `default-directory` >> for the next command, but with a closure the variable binding will have >> the effect during the next command. > > This sounds like it might benefit from using a trick like the one I use > in `mule-cmds--prefixed-command-pch` in order to let-bind > `coding-system-for-read/write` around the call of the next command. It's surprising that such trick works without problems. And it seems it's exactly what is needed for `project-switch-project`. I could try to generalize it to support modification of arbitrary variables.