[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Comma
From: |
Sean Whitton |
Subject: |
Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording. |
Date: |
Fri, 30 Sep 2022 16:46:51 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Hello Eli,
Thank you for reviewing the commit.
On Fri 30 Sep 2022 at 02:57PM -04, Eli Zaretskii wrote:
> diff --git a/doc/emacs/vc1-xtra.texi b/doc/emacs/vc1-xtra.texi
> index a8ceb1b790..05d2144380 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.
I would like to restore the idea that it's about accessing VC
system-specific features, because adding optional command line arguments
is merely the means by which they are accessed. How about:
This is primarily intended to make it possible to access version
control system-specific functionality, by means of adding optional
command line arguments to VCS commands, without unwanted
complications of the VC command set and its interfaces with the
backend.
--
Sean Whitton
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording.,
Sean Whitton <=