From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: Emacs-Hacker2017@jovi.net, 28609@debbugs.gnu.org
Subject: bug#28609: simple.el
Date: Sat, 30 Sep 2017 11:12:51 +0300 [thread overview]
Message-ID: <83wp4g4nb0.fsf@gnu.org> (raw)
In-Reply-To: <0fe74dd5-598d-47c0-b734-221170345be7@default> (message from Drew Adams on Fri, 29 Sep 2017 19:30:40 -0700 (PDT))
> Date: Fri, 29 Sep 2017 19:30:40 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 28609@debbugs.gnu.org
>
> > Finally, a nit: "Point position" is inherently ambiguous, so it's
> > better to use "Position of point" to disambiguate. I made that change
> > in a followup commit.
>
> Apologies for not reading the thread. Going only by what is written
> here, which might not be fair/appropriate, "position of point" is
> also ill-advised. "Point" is the buffer position of the cursor
> (text-insertion position). "Position of point" would then mean
> "position of position of the cursor".
"Point" is Emacs terminology (and its definition in Glossary is not
"position of the cursor"). Since it's a widely-used term, I see no
need to replace "point" with its definition to judge that sentence's
grammar or style. We use "position of point" in our manuals, and I
see no problem with that usage.
next prev parent reply other threads:[~2017-09-30 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<D4ACD8F1-C378-4363-B319-1DADFCB639EF@jovi.net>
[not found] ` <<838tgx8xpa.fsf@gnu.org>
2017-09-30 2:30 ` bug#28609: simple.el Drew Adams
2017-09-30 8:12 ` Eli Zaretskii [this message]
2017-09-26 14:51 Devon Sean McCullough
2017-09-26 16:28 ` John Wiegley
2017-09-26 16:33 ` John Wiegley
2017-09-26 19:09 ` Johan Bockgård
2017-09-26 19:37 ` John Wiegley
2017-09-29 13:28 ` Eli Zaretskii
2017-09-30 11:09 ` Johan Bockgård
2017-10-04 20:24 ` Johan Bockgård
2017-10-05 8:33 ` Eli Zaretskii
2020-08-22 19:23 ` Stefan Kangas
2017-09-29 13:02 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83wp4g4nb0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28609@debbugs.gnu.org \
--cc=Emacs-Hacker2017@jovi.net \
--cc=drew.adams@oracle.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.