From: Dmitry Gutov <dmitry@gutov.dev>
To: Juri Linkov <juri@linkov.net>
Cc: 70577@debbugs.gnu.org
Subject: bug#70577: [PATCH] New command other-project-prefix
Date: Fri, 26 Apr 2024 13:59:48 +0300 [thread overview]
Message-ID: <a8483157-e2dd-409f-8a6c-08f5e339defc@gutov.dev> (raw)
In-Reply-To: <86le501ykg.fsf@mail.linkov.net>
On 26/04/2024 09:09, Juri Linkov wrote:
>> This is based on Juri's patch in
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=63648#161, but the idea is
>> more focused: to switch the order of events, and first read the full key
>> sequence, and then prompt for the project and the command arguments. Like
>> we also discussed in the past.
>
> I'm not a fan of reading the full key sequence bypassing the event loop.
That's what the current code does. While the patch tries to change that.
>> And to try to reuse the even loop in the more natural way. Unfortunately,
>> 'C-h' doesn't work here (when called in the middle of the sequence) - I'm
>> not sure why. The rest of the behavior seems to work as expected.
>
> 'C-h' can't work since 'C-x p p' is bound to a command.
Hmm, I wonder how hard it'd be to change that.
>> So this can be a new alternative for the 'C-x p p' binding as well.
>
> I guess there could be 2 new alternative options for 'project-switch-commands':
>
> 1. read the full key sequence
> 2. use the event loop with set-transient-map
>
> Although I'm already completely content with the existing option
> 'project-prefix-or-any-command' of 'project-switch-commands'.
This one is indeed an experiment. It just seems that being able to type
the full sequence first is more ergonomically advantageous.
But overall this (adding a +1 alternative) is probably only worth it if
we can make 'C-h' work like normal.
next prev parent reply other threads:[~2024-04-26 10:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 3:01 bug#70577: [PATCH] New command other-project-prefix Dmitry Gutov
2024-04-26 6:09 ` Juri Linkov
2024-04-26 10:59 ` Dmitry Gutov [this message]
2024-04-26 16:20 ` Dmitry Gutov
2024-04-28 12:13 ` Sean Whitton via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-28 15:56 ` Dmitry Gutov
2024-04-28 16:51 ` Juri Linkov
2024-04-28 21:40 ` Dmitry Gutov
2024-05-02 6:12 ` Juri Linkov
2024-05-04 2:12 ` Dmitry Gutov
2024-05-04 7:24 ` Eli Zaretskii
2024-05-04 17:22 ` Dmitry Gutov
2024-05-04 17:34 ` Eli Zaretskii
2024-05-05 0:02 ` Dmitry Gutov
2024-05-05 5:44 ` Eli Zaretskii
2024-05-05 18:26 ` Dmitry Gutov
2024-05-05 16:40 ` Juri Linkov
2024-05-05 18:55 ` Dmitry Gutov
2024-05-06 17:25 ` Juri Linkov
2024-05-06 18:30 ` Juri Linkov
2024-05-07 19:23 ` Dmitry Gutov
2024-05-09 6:24 ` Juri Linkov
2024-05-07 19:16 ` Dmitry Gutov
2024-05-09 2:22 ` Dmitry Gutov
2024-05-09 6:20 ` Juri Linkov
2024-05-10 1:46 ` Dmitry Gutov
2024-05-10 6:43 ` Juri Linkov
2024-05-10 15:09 ` Dmitry Gutov
2024-05-12 18:33 ` Dmitry Gutov
2024-05-14 6:23 ` Juri Linkov
2024-05-14 20:02 ` Dmitry Gutov
2024-05-15 6:46 ` Juri Linkov
2024-05-21 2:31 ` Dmitry Gutov
2024-05-21 6:08 ` Juri Linkov
2024-05-21 20:16 ` Dmitry Gutov
2024-05-22 6:12 ` Juri Linkov
2024-05-23 6:24 ` Juri Linkov
2024-05-26 2:38 ` Dmitry Gutov
2024-05-26 6:52 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8483157-e2dd-409f-8a6c-08f5e339defc@gutov.dev \
--to=dmitry@gutov.dev \
--cc=70577@debbugs.gnu.org \
--cc=juri@linkov.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).