From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: master 1d4862e: Fix English grammar in some doc strings and comments Date: Tue, 05 Nov 2019 22:28:03 -0500 Message-ID: References: <14407.1572888070@quatro> <8736f3js95.fsf@fastmail.fm> <871runxqjq.fsf@gmx.net> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="44120"; mail-complaints-to="usenet@blaine.gmane.org" Cc: joostkremers@fastmail.fm, lekktu@gmail.com, emacs-devel@gnu.org To: Stephen Berman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 06 04:28:25 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iSBza-000BF3-PX for ged-emacs-devel@m.gmane.org; Wed, 06 Nov 2019 04:28:22 +0100 Original-Received: from localhost ([::1]:52528 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSBzY-0006QR-TW for ged-emacs-devel@m.gmane.org; Tue, 05 Nov 2019 22:28:20 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:50600) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iSBzJ-0006QD-HM for emacs-devel@gnu.org; Tue, 05 Nov 2019 22:28:06 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39161) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iSBzJ-00037h-AO; Tue, 05 Nov 2019 22:28:05 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.82) (envelope-from ) id 1iSBzH-0002Eq-Cj; Tue, 05 Nov 2019 22:28:03 -0500 In-Reply-To: <871runxqjq.fsf@gmx.net> (message from Stephen Berman on Mon, 04 Nov 2019 22:47:05 +0100) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:241840 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. ]]] > Such examples may > be contrasted with those in [52], where there is significantly greater > potential for misinterpretation, and hence a stronger case for > recommending that /only/ be placed next to the intended focus: > [52] i You can only access the web at this workstation. > ii Last Christmas he only gave money to his children. This is the practical reason for being careful where to place "only" in a written text. It is true that other positioning for "only" is not inherently wrong. It merely risks ambiguity. But avoiding ambiguity is a proper goal in writing documentation. Thus, a rule about where to place "only" may be a wise policy, even though grammar does not exactly require it. -- Dr Richard Stallman Founder, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)