all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: "whether the global keymap C-x 4 will be replaced by a command,"
Date: Thu, 16 Jul 2020 00:07:25 -0400	[thread overview]
Message-ID: <jwvk0z4t8lw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87y2nkbah5.fsf@mail.linkov.net> (Juri Linkov's message of "Thu,  16 Jul 2020 02:54:30 +0300")

> Then it could bind `overriding-terminal-local-map` (instead of using
> `set-transient-map`)

Not sure what's the difference.

> 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`.

> 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.


        Stefan




  reply	other threads:[~2020-07-16  4:07 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1juSI3-0005ai-6j@fencepost.gnu.org>
     [not found] ` <83ft9woo68.fsf@gnu.org>
2020-07-13  2:52   ` "whether the global keymap ‘C-x 4’ will be replaced by a command," Richard Stallman
2020-07-13 23:58     ` "whether the global keymap C-x 4 " Juri Linkov
2020-07-14  4:19       ` Drew Adams
2020-07-14  5:55       ` Stefan Monnier
2020-07-14 14:41         ` Drew Adams
2020-07-14 14:48           ` Stefan Monnier
2020-07-14 15:28             ` Drew Adams
2020-07-14 15:35           ` John Yates
2020-07-14 14:51         ` Eli Zaretskii
2020-07-14 15:15           ` Stefan Monnier
2020-07-14 16:29             ` Eli Zaretskii
2020-07-15  4:06               ` Stefan Monnier
2020-07-15 14:16                 ` Eli Zaretskii
2020-07-15 23:54                 ` Juri Linkov
2020-07-16  4:07                   ` Stefan Monnier [this message]
2020-07-16 22:57                     ` Juri Linkov
2020-07-17  2:56                       ` Stefan Monnier
2020-07-17  0:56                 ` Richard Stallman
2020-07-14 22:27         ` Juri Linkov
2020-07-14 22:55           ` Drew Adams
2020-07-15  4:06           ` Stefan Monnier
2020-07-16  3:21           ` Richard Stallman
2020-07-16 15:05             ` Eli Zaretskii
2020-07-16 23:05             ` Juri Linkov
2020-07-17  2:10               ` Drew Adams
2020-07-18  1:57                 ` Richard Stallman
2020-07-18 16:23                   ` Sean Whitton
2020-07-18 17:00                     ` Drew Adams
2020-07-19  2:28                     ` Richard Stallman
2020-07-19 15:28                       ` Drew Adams
2020-07-21  0:22                       ` Sean Whitton
2020-07-18  1:54               ` Richard Stallman
2020-07-18 23:21                 ` Juri Linkov
2020-07-19  0:11                   ` Drew Adams
2020-07-19  3:38                   ` Stefan Monnier
2020-07-19 22:07                     ` Juri Linkov
2020-07-20  3:09                       ` Stefan Monnier
2020-07-20 20:50                         ` Juri Linkov
2020-07-20  2:39                   ` Richard Stallman
2020-07-20  3:13                   ` Stefan Monnier
2020-07-15  3:32         ` Richard Stallman
2020-07-19 13:00           ` Barry Fishman
2020-07-19 15:38             ` Drew Adams
2020-07-19 16:20               ` Barry Fishman
2020-07-19 17:45                 ` Drew Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk0z4t8lw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=rms@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.