unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Siraphob (Ben) Phipathananunth" <siraben@disroot.org>,
	emacs-devel@gnu.org
Subject: RE: "Point" vs. "cursor" in documentation
Date: Wed, 4 Jul 2018 07:52:50 -0700 (PDT)	[thread overview]
Message-ID: <9b6fb4b7-f9a3-4f96-9b2a-86b744892d48@default> (raw)
In-Reply-To: <0a994a51-b80b-9d78-9e9e-0d379ffa5733@disroot.org>

> Right.  I've seen the explanation.  It's like hell|o where | is the
> position of point, and cursor appears over the "o".
> 
> When do we use point over cursor, and vice versa, in documentation?

If the | is something visual, it indicates a position.
If it is the cursor then it indicates point.  That's
what the cursor does: it indicates the position (point)
where text is inserted when you type.

One (point) is the position.  The other (cursor) is
a visual indication of that position.  Even if the
cursor were removed (not displayed), point would be
there - it's just a buffer position (1 ...).

When you want to talk about the position where text
will be inserted etc., use "point".  When you want
to talk about the display artifact that indicates
that position (whether shown as bar, box, this color
or that), use "cursor".



      parent reply	other threads:[~2018-07-04 14:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03 13:25 "Point" vs. "cursor" in documentation Siraphob (Ben) Phipathananunth
2018-07-03 14:27 ` Drew Adams
2018-07-03 14:37   ` Jean-Christophe Helary
2018-07-03 20:16     ` John Yates
2018-07-03 23:04       ` Richard Stallman
2018-07-04 12:13         ` John Yates
2018-07-04 15:15           ` Eli Zaretskii
2018-07-04 17:20             ` Drew Adams
2018-07-04 22:32           ` Richard Stallman
2018-07-04 23:03             ` John ff
2018-07-04  2:27   ` Siraphob (Ben) Phipathananunth
2018-07-04  2:39     ` Stefan Monnier
2018-07-04  6:21       ` Jean-Christophe Helary
2018-07-04 14:52     ` Drew Adams [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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9b6fb4b7-f9a3-4f96-9b2a-86b744892d48@default \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=siraben@disroot.org \
    /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.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).