From: Sebastian Miele <sebastian.miele@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Typo in Org Manual
Date: Fri, 06 Mar 2020 10:43:51 +0100 [thread overview]
Message-ID: <87blp9rf6w.fsf@gmail.com> (raw)
In-Reply-To: <875zfi851k.fsf@kyleam.com>
Kyle Meyer <kyle@kyleam.com> writes:
>
> Sebastian Miele <sebastian.miele@gmail.com> writes:
>
> > In an example for Org table range references it says:
> >
> > ‘@2$1..@4$3’ six fields between these two fields (same as ‘A2..C4’)
>
> 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 ‘..’.
to
You may reference a rectangular range of fields, including the ends,
by specifying two field references connected by two dots ‘..’.
?
next prev parent reply other threads:[~2020-03-06 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 13:32 Typo in Org Manual Sebastian Miele
2020-03-06 4:45 ` Kyle Meyer
2020-03-06 9:43 ` Sebastian Miele [this message]
2020-03-06 9:54 ` Sebastian Miele
2020-03-06 18:04 ` Nick Dokos
2020-03-07 4:14 ` Kyle Meyer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blp9rf6w.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=kyle@kyleam.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).