From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 65558@debbugs.gnu.org, Pengji Zhang <kunhtkun@gmail.com>
Subject: bug#65558: 30.0.50; project-other-{window,frame,tab}-command a bit too obtrusive
Date: Thu, 19 Oct 2023 20:49:10 +0300 [thread overview]
Message-ID: <868r7ywmfo.fsf@mail.linkov.net> (raw)
In-Reply-To: <dbc2c8be-ef84-4a9c-abf9-24e261d2c15f@gutov.dev> (Dmitry Gutov's message of "Thu, 19 Oct 2023 15:40:35 +0300")
>>> Thanks for the pointer! That is a long thread so I only skimmed it. I
>>> think you meant this snippet in [0]:
>>>
>>>> (defun project-other-window-command ()
>>>> (interactive)
>>>> (other-window-prefix)
>>>> (set-transient-map (make-composed-keymap project-prefix-map
>>>> project-other-window-map)))
>> Exactly. And the same for the frame command in the most recent patch
>> I posted to bug#63648, and I confirm that your bug report is fixed with it.
>>
>>> That indeed fixes the issue. My only concern is that
>>> `other-window-prefix' is a new function introduced in Emacs 28.
>> Indeed, it would take more efforts to provide backward-compatibility
>> for older Emacs versions.
>
> I think we can install this (tweaked) part of your changes from that other
> bug to close this report.
Since it could be installed independently from bug#63648,
I think it would be nice to close this bug report with this patch.
> +;; TODO: maybe rename to project-other-window-prefix
> ;;;###autoload (define-key ctl-x-4-map "p" #'project-other-window-command)
Maybe this TODO not needed anymore?
next prev parent reply other threads:[~2023-10-19 17:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 19:25 bug#65558: 30.0.50; project-other-{window,frame,tab}-command a bit too obtrusive Pengji Zhang
2023-08-27 16:13 ` Juri Linkov
2023-08-30 3:58 ` Pengji Zhang
2023-08-30 16:50 ` Juri Linkov
2023-10-19 12:40 ` Dmitry Gutov
2023-10-19 17:49 ` Juri Linkov [this message]
2023-10-19 18:31 ` Dmitry Gutov
2023-10-19 18:51 ` Juri Linkov
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=868r7ywmfo.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=65558@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=kunhtkun@gmail.com \
/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.