From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Miele Subject: Re: Typo in Org Manual Date: Fri, 06 Mar 2020 10:43:51 +0100 Message-ID: <87blp9rf6w.fsf@gmail.com> References: <87eeu8kzyj.fsf@gmail.com> <875zfi851k.fsf@kyleam.com> Reply-To: sebastian.miele@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57055) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jA9WP-0008GW-IU for emacs-orgmode@gnu.org; Fri, 06 Mar 2020 04:43:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jA9WO-0006Gm-F5 for emacs-orgmode@gnu.org; Fri, 06 Mar 2020 04:43:57 -0500 Received: from mail-wm1-x332.google.com ([2a00:1450:4864:20::332]:50714) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jA9WO-00069O-7w for emacs-orgmode@gnu.org; Fri, 06 Mar 2020 04:43:56 -0500 Received: by mail-wm1-x332.google.com with SMTP id a5so1629532wmb.0 for ; Fri, 06 Mar 2020 01:43:55 -0800 (PST) In-reply-to: <875zfi851k.fsf@kyleam.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: Kyle Meyer Cc: emacs-orgmode@gnu.org Kyle Meyer writes: > > Sebastian Miele writes: > > > In an example for Org table range references it says: > > > > =E2=80=98@2$1..@4$3=E2=80=99 six fields between these two fields (sam= e as =E2=80=98A2..C4=E2=80=99) > > Oh, that mistake has been around for a long time. > > > However, it are nine fields instead of six. > > If we were to simply replace "six" with "nine", I think the > description could still be confusing because it's ambiguous whether > "between" includes the ends. (I would tend to read the above > description as exclusive.) At least for me, "nine" would not be confusing at all, because among the sensible interpretations of the range specification, "nine" uniquely identifies the maximally inclusive one. If it were a problem, then the preceding and following examples all have the same problem, too, except maybe the hline example. > How about "nine fields between and including these two fields"? Any > other suggestions? In my opinion this is not necessary. The examples (assuming "nine" instead of "six") make it clear enough, that always the maximally inclusive sensible interpretation of the range specification is used. But how about instead changing the first sentence of the "Range references" section from You may reference a rectangular range of fields by specifying two field references connected by two dots =E2=80=98..=E2=80=99. to You may reference a rectangular range of fields, including the ends, by specifying two field references connected by two dots =E2=80=98..=E2= =80=99. ?