From: Kyle Meyer <kyle@kyleam.com>
To: sebastian.miele@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Typo in Org Manual
Date: Sat, 07 Mar 2020 04:14:28 +0000 [thread overview]
Message-ID: <87zhcs7qe3.fsf@kyleam.com> (raw)
In-Reply-To: <87blp9rf6w.fsf@gmail.com>
Sebastian Miele <sebastian.miele@gmail.com> writes:
> Kyle Meyer <kyle@kyleam.com> writes:
>> 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.
Fair enough.
> If it were a problem, then the preceding and following examples all have
> the same problem, too, except maybe the hline example.
Hmm, I looked over those before sending the email and didn't find any of
them ambiguous. Perhaps I'm just inclined to read "between" ambiguously
and gloss over everything else. Either way...
Later Sebastian Miele <sebastian.miele@gmail.com> writes:
> Sebastian Miele <sebastian.miele@gmail.com> writes:
>>
>> 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 ‘..’.
>>
>> ?
>
> I think even better would be to just add the following after the
> sentence mentioned above:
>
> The ends are included in the range.
... this sounds good to me. I went with that, along with replacing
"six" with "nine".
Thanks for the suggestion and for catching the error.
prev parent reply other threads:[~2020-03-07 4:14 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
2020-03-06 9:54 ` Sebastian Miele
2020-03-06 18:04 ` Nick Dokos
2020-03-07 4:14 ` Kyle Meyer [this message]
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=87zhcs7qe3.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian.miele@gmail.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).