From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording. Date: Fri, 07 Oct 2022 15:45:17 +0300 Message-ID: <83y1trn6oy.fsf@gnu.org> References: <166456427452.19714.6372202545661875453@vcs2.savannah.gnu.org> <20220930185754.DF8FAC00615@vcs2.savannah.gnu.org> <877d1k8lxw.fsf@melete.silentflame.com> <83bkqwccvv.fsf@gnu.org> <87tu4j2mvr.fsf@melete.silentflame.com> <83tu4iu80n.fsf@gnu.org> <875ygx27ma.fsf@melete.silentflame.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8426"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Sean Whitton Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Oct 07 16:24:17 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ogoGt-0001yo-Nu for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 16:24:15 +0200 Original-Received: from localhost ([::1]:42264 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ogoGs-0002wS-Nc for ged-emacs-devel@m.gmane-mx.org; Fri, 07 Oct 2022 10:24:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34496) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogmj9-0008Av-77 for emacs-devel@gnu.org; Fri, 07 Oct 2022 08:45:20 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:52648) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogmj8-0005eI-P8; Fri, 07 Oct 2022 08:45:18 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=2gwYLgRXkP2CtvJ0+bymg7yuVoOE+9SPLReX+FLiiWQ=; b=PZmaY1Bkkuz6 Uu1XdCy9zjt1NKSk3S/sfuIf1ditU/rHQPYxbCukD7I5AC8rX7JTbmZM2DpdofTf3B6rCowbXI5yt UrVci5bAcdnfV43qoVpxUCT52CaA4IxL5YG8xFg9QPBiich+Fo/oL8YtehyNL9yAEYrMvInAVpKPt FfAgnCS0dydYghDCgC/SToD5ZiX9NWpmMkHJg6XQqRHeErYMd1LHsDQZIDxL2WRk4ILt/dX9zyPwv 0kAvRf2yZvodT+nCoFoz4MIxFYTnotwKBER469YcjXmZIqMCcLa+aLm7ZGO48HeHgLf8iD/6S7pLY //uMQn1ePgO/2zG32lZFpQ==; Original-Received: from [87.69.77.57] (port=2323 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ogmj8-0001Nu-6v; Fri, 07 Oct 2022 08:45:18 -0400 In-Reply-To: <875ygx27ma.fsf@melete.silentflame.com> (message from Sean Whitton on Wed, 05 Oct 2022 16:06:21 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:297150 Archived-At: > From: Sean Whitton > Cc: emacs-devel@gnu.org > Date: Wed, 05 Oct 2022 16:06:21 -0700 > > 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. I very much doubt that you can usefully say something like that in a description of an obscure command: how will that be discovered? And where else in the manual would you say something like that, when it involves a specific command? So maybe say that in NEWS?