From f7b84345f8e646d7c1ac26551d7f8363ccf78222 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Fri, 30 Sep 2022 21:55:38 +0300 Subject: [PATCH] ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording. --- doc/emacs/vc1-xtra.texi | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/doc/emacs/vc1-xtra.texi b/doc/emacs/vc1-xtra.texi index a8ceb1b7906..05d21443804 100644 --- a/doc/emacs/vc1-xtra.texi +++ b/doc/emacs/vc1-xtra.texi @@ -270,16 +270,17 @@ with the file's version control type. @findex vc-edit-next-command @kindex C-x v ! You can use the @kbd{C-x v !} (@code{vc-edit-next-command}) prefix -command to request an opportunity to edit the VC shell commands that -Emacs will run. This is primarily intended to make it possible to -access version control system-specific functionality without -complexifying either the VC command set or the backend API. +command to edit the shell command line that VC is about to run. This +is primarily intended to make it possible to add optional command-line +arguments to VCS commands without unnecessary complications of the VC +command set and its interfaces with the backend. For example, Git can produce logs of more than one branch, but @kbd{C-x v b l} (@code{vc-print-branch-log}) prompts for the name of just one branch. To obtain a log of more than one branch, you can -type @kbd{C-x v ! C-x v b l} and then append the names of additional -branches to the end of the @code{git log} command that VC prepares. +type @w{@kbd{C-x v ! C-x v b l}} and then append the names of +additional branches to the end of the @samp{git log} command that VC +is about to run. @node Customizing VC @subsection Customizing VC -- 2.39.2