From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 70577@debbugs.gnu.org
Subject: bug#70577: [PATCH] New command other-project-prefix
Date: Sun, 05 May 2024 19:40:14 +0300 [thread overview]
Message-ID: <865xvsjklh.fsf@mail.linkov.net> (raw)
In-Reply-To: <c062e78a-6145-4ea5-baa7-27d948f8a758@gutov.dev> (Dmitry Gutov's message of "Sat, 4 May 2024 05:12:39 +0300")
> We would want 'C-h' to show the regular buffer with key bindings, won't we?
> With similar output to the one that we get after 'C-x p C-h' or 'C-x
> v C-h'. The output might be weirder because of the composed keymap, but it
> could still be useful.
Then maybe something like
(define-key map (vector help-char)
(lambda () (interactive) (describe-bindings)))
or
(define-key map (vector help-char)
(lambda () (interactive) (describe-keymap (cons 'keymap (current-active-maps)))))
or
(define-key map (vector help-char)
(lambda () (interactive) (describe-keymap (cons 'keymap project-prefix-map))))
>> However, a much bigger problem is that unfortunately many test cases from
>> https://debbugs.gnu.org/63648#203 are broken. For example,
>> 'C-x p p C-b' fails the same way as in bug#58784.
>> 'C-x p p f M-n' fails because it expects to read arguments
>> in a previous project with an old value of default-directory, etc.
>
> Thanks for noticing. Looks like the call to project-prompter can change the
> value of this-command, and that's why the subsequent check went down the
> wrong branch. See the attached v3 with the fix.
Wow, everything works now, will test more as a primary 'C-x p p' command.
next prev parent reply other threads:[~2024-05-05 16:40 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
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 [this message]
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=865xvsjklh.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=70577@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
/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).