unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: 63690@debbugs.gnu.org
Subject: bug#63690: 29.0.91; New vc commands missing on vc-menu
Date: Wed, 24 May 2023 19:16:23 +0300	[thread overview]
Message-ID: <86cz2q404g.fsf@mail.linkov.net> (raw)

etc/NEWS on emacs-29 contains:

  'vc-print-branch-log' is bound to 'C-x v b l', and new commands are
  'vc-create-branch' ('C-x v b c') and 'vc-switch-branch' ('C-x v b s').

But new commands are not yet added to 'vc-menu-map'.
This patch for emacs-29 fixes this omission:

diff --git a/lisp/vc/vc-hooks.el b/lisp/vc/vc-hooks.el
index 02c4a240c6a..402b918fc7d 100644
--- a/lisp/vc/vc-hooks.el
+++ b/lisp/vc/vc-hooks.el
@@ -898,6 +927,15 @@ vc-menu-map
     (bindings--define-key map [vc-create-tag]
       '(menu-item "Create Tag" vc-create-tag
 		  :help "Create version tag"))
+    (bindings--define-key map [vc-print-branch-log]
+      '(menu-item "Show Branch History" vc-print-branch-log
+		  :help "Show the change log for branch root"))
+    (bindings--define-key map [vc-switch-branch]
+      '(menu-item "Switch Branch" vc-switch-branch
+		  :help "Switch to the branch"))
+    (bindings--define-key map [vc-create-branch]
+      '(menu-item "Create Branch" vc-create-branch
+		  :help "Make a new branch"))
     (bindings--define-key map [separator1] menu-bar-separator)
     (bindings--define-key map [vc-annotate]
       '(menu-item "Annotate" vc-annotate





             reply	other threads:[~2023-05-24 16:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 16:16 Juri Linkov [this message]
2023-05-24 16:51 ` bug#63690: 29.0.91; New vc commands missing on vc-menu Eli Zaretskii
2023-05-24 17:31   ` Juri Linkov
2023-05-24 18:39     ` Eli Zaretskii
2023-05-25  6:43       ` Juri Linkov
2023-05-25  7:50         ` Eli Zaretskii
2023-05-25 18:25           ` 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=86cz2q404g.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=63690@debbugs.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 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).