From: Sean Whitton <spwhitton@spwhitton.name>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording.
Date: Wed, 05 Oct 2022 16:06:21 -0700 [thread overview]
Message-ID: <875ygx27ma.fsf@melete.silentflame.com> (raw)
In-Reply-To: <83tu4iu80n.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Oct 2022 08:58:00 +0300")
Hello,
On Wed 05 Oct 2022 at 08:58AM +03, Eli Zaretskii wrote:
> "Would not make much sense" is in the eyes of the beholder. Not all
> of us are quick-thinking enough to realize the commands we sometimes
> choose to do a job are not the optimal ones. But there's no reason to
> pretend that there's only one way of doing every job.
>
> Are there other reasons to insist on the "VCS-specific functionality"
> aspect of this command, beyond the above considerations of using VC
> command in an optimal fashion?
What I'd like to get across in the manual, somehow and somewhere, is
that VC now has a broadly applicable answer to the question of accessing
VCS-specific functionality. We've decided that in many cases, the best
thing is to require that the user edit command lines themselves, rather
than adding new VC commands or new VCS-specific commands. So if someone
is wondering "how do I get at X with VC, do I just have to resort to a
shell?" it would be good for them to know that 'C-x v !' might be a
convenient option for them.
I accept that here is perhaps not the best place to try to get this
across. Where do you think something like that might fit? Would be
grateful for help.
--
Sean Whitton
next prev parent reply other threads:[~2022-10-05 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166456427452.19714.6372202545661875453@vcs2.savannah.gnu.org>
[not found] ` <20220930185754.DF8FAC00615@vcs2.savannah.gnu.org>
2022-09-30 23:46 ` master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording Sean Whitton
2022-10-01 5:48 ` Eli Zaretskii
2022-10-04 23:24 ` Sean Whitton
2022-10-05 5:58 ` Eli Zaretskii
2022-10-05 23:06 ` Sean Whitton [this message]
2022-10-07 12:45 ` Eli Zaretskii
2023-02-22 17:19 ` Sean Whitton
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=875ygx27ma.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).