From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Sean Whitton Newsgroups: gmane.emacs.devel Subject: Re: master f7b84345f8 1/2: ; * doc/emacs/vc1-xtra.texi (Editing VC Commands): Fix wording. Date: Wed, 22 Feb 2023 10:19:12 -0700 Message-ID: <875ybtd3e7.fsf@melete.silentflame.com> 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> <83y1trn6oy.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33433"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Feb 22 18:19:52 2023 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 1pUsmV-0008X9-4M for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Feb 2023 18:19:51 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pUsm2-0001we-C6; Wed, 22 Feb 2023 12:19:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUslz-0001pL-Fj for emacs-devel@gnu.org; Wed, 22 Feb 2023 12:19:20 -0500 Original-Received: from out5-smtp.messagingengine.com ([66.111.4.29]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pUslx-0000WC-QP; Wed, 22 Feb 2023 12:19:19 -0500 Original-Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 67B135C0094; Wed, 22 Feb 2023 12:19:14 -0500 (EST) Original-Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Wed, 22 Feb 2023 12:19:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spwhitton.name; h=cc:cc:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1677086354; x=1677172754; bh=ym hbLTbG25qoxtfLhUak+Vw5xPt7vA2/VHoFmHC31bM=; b=QhulbI4mSGv+aWlbgm Q8XmY5sl0U/12SNQqisq6y8XqVaVKDLoymTY9S7LrhFaVUPliwwq7U3R2O+7v7iq 7Ws9foeg3sFUh0y/RF5kc2c284oVo8b8wJIZnc0ZwIxB/uSWarWkf5sZE+q0cMQZ 7njK0LbjViQF3YDpn/ccjdwFOcHfVCEClD3/DX5qKznpNyD3FgaJRIloSPwOhDdm +a6qqKsy0NeTCO4JN51+H0ifJzyJGMipotVFgjCTCJqlf7vis7fFa1trP3vf2xhp J7X53DTu8FMtOC5mkWhKh7HQRqAcJsvL5RBc4INilwOEUJ/39GoHncbEQ5BABCfH gQvA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1677086354; x=1677172754; bh=ymhbLTbG25qoxtfLhUak+Vw5xPt7 vA2/VHoFmHC31bM=; b=DjUQiMsIy0g+BlnytCKGgPuXor7fZfw70QyRLL42bLM5 hxwTvAcBEN5pAVJD+bAp8C6cOGC20fAPK2XJPwZFk/JPrp/f7amfvwGaEixqviQx VqJmCexL1ZxseWx3Xs+9WsLO8v6u8vK5ZNzK0RZBdQ4bcZ82TA80o0soOr4WrA7P LYnSC0l2a0aEEirpCc7dtYc05/uaYJ0eKbTtqP8hwxvO1FsO3Ks2byIW29owypr8 m5X76suwb8cMkdQjBc+uEZbOMMw8TgZDLxj/pJdemqw9f6BJ2i7+Acqb7BOpU3sD QXOsgFfWnwD2c9jiE+sJIzawub/H2CYuB8EYXLT3fQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudejledgleekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefujghffffkfgggtgesthdttddttdertdenucfhrhhomhepufgvrghn ucghhhhithhtohhnuceoshhpfihhihhtthhonhesshhpfihhihhtthhonhdrnhgrmhgvqe enucggtffrrghtthgvrhhnpedtffdvffeuleeuvdetkedvveehgfehvdegvefghfevudek geegleevgeejkeetkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehsphifhhhithhtohhnsehsphifhhhithhtohhnrdhnrghmvg X-ME-Proxy: Feedback-ID: i23c04076:Fastmail Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 22 Feb 2023 12:19:14 -0500 (EST) Original-Received: by melete.silentflame.com (Postfix, from userid 1000) id 525A87EC297; Wed, 22 Feb 2023 10:19:12 -0700 (MST) In-Reply-To: <83y1trn6oy.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 07 Oct 2022 15:45:17 +0300") Received-SPF: pass client-ip=66.111.4.29; envelope-from=spwhitton@spwhitton.name; helo=out5-smtp.messagingengine.com X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:303685 Archived-At: Hello, On Fri 07 Oct 2022 at 03:45PM +03, Eli Zaretskii wrote: >> 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? Yes, good point. > And where else in the manual would you say something like that, when > it involves a specific command? Not sure. > So maybe say that in NEWS? Okay, thanks for the suggestion, now done. -- Sean Whitton