From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: feature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistenciesfeature/eglot-texi-manual 4725c123f3 2/5: ; eglot.texi: Fix typos and minor inconsistencies Date: Sat, 22 Oct 2022 15:59:51 -0400 Message-ID: References: <83h6zyye3f.fsf@gnu.org> <87ilkeu3r1.fsf@gmail.com> <87a65qty8a.fsf@gmail.com> <83a65qy57n.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40937"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rpluim@gmail.com, stefankangas@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 24 06:56:49 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 1ompW4-000AQ0-TF for ged-emacs-devel@m.gmane-mx.org; Mon, 24 Oct 2022 06:56:48 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1omjNT-0001OC-G2 for ged-emacs-devel@m.gmane-mx.org; Sun, 23 Oct 2022 18:23:31 -0400 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 1omKeu-0002lW-8q for emacs-devel@gnu.org; Sat, 22 Oct 2022 15:59:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1omKeu-0003jV-18; Sat, 22 Oct 2022 15:59:52 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=r9dU17biqAKE518FfESHKzjCPdlfmqh8ZY8IekhveqU=; b=YLUWUuL46N8E s/c+gyZCgz2VqxY4UFnrm75ElnqnLvR0Sxpm0ETXi912Zzb4YE09afRVyqUNLqg0f+OsJhtpB3lm4 1grhi+vUkjzrQF8WCHj/FZ4ECZV2WcK4MUtQ7jJE/dyN+Pc4ymEQeuroNfifcg2+yNGlHinwPWkK/ BhvdOL0ejq96KuHyyBnLHWIISUvCdrACvJ6IjB6ytPfQK+zNFQ1mpajI/VuYqoZXJv8d+vFosy3yF SpNtsxf0ussy1JZY1tiHGSYPdRZxw5tcFNG94DTyDhbhLpQ+03/sYxrkAeKCe/4fLLAll0VY4H2tm jjhwlvMPPOd6ujbSXuVahA==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1omKet-00018t-OG; Sat, 22 Oct 2022 15:59:51 -0400 In-Reply-To: <83a65qy57n.fsf@gnu.org> (message from Eli Zaretskii on Thu, 20 Oct 2022 16:50:20 +0300) 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:298319 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > > You donʼt want progressive, you want conservative: if the existing > > text is not clearly incorrect, donʼt change it, even if thereʼs some > > guide that says itʼs 'wrong'. > Exactly. We should always err on that side, out of respect to the > original author(s) if for no other reasons. Please try following this > principle. Nothing about Eglot is "existing text" as far as Emacs is concerned. All of it is proposed to add. If we see ways to improve it before we add it, we should do so. Better now than later. Consistency of style is a virtue in documentation, and so is consistency of terminology. These are important reasons to make documentation text more uniform when installing it. We are not all equally skilled in writing clear English text. We should improve the writing that contributors submit. Documemtation shuld be structured according to the concepts of use, not based on implementation. THe basic question here is, should we ask users to think in terms of "documenting hwo to use Eglot" or in terms of "documenting various features" (which happen to be provided by Eglot)? People seem to have assumed the former, but we ought to consider the latter too, and see which approach will be easiest to understand. Would someone please show me the documentation about Eglot? -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)