From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 38051@debbugs.gnu.org, stefan@marxist.se
Subject: bug#38051: 26.3; (elisp) `Insertion' use of verb "point"
Date: Fri, 08 Nov 2019 21:11:38 +0200 [thread overview]
Message-ID: <83a796b2tx.fsf@gnu.org> (raw)
In-Reply-To: <3b0f7464-a74f-4687-b91b-b654697cc1cc@default> (message from Drew Adams on Fri, 8 Nov 2019 17:53:06 +0000 (UTC))
> Date: Fri, 8 Nov 2019 17:53:06 +0000 (UTC)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: 38051@debbugs.gnu.org
>
> 1. From a user point of view (conceptual model),
> markers _are_ objects that can be located
> _in_ a buffer, _at_ buffer positions.
That is incorrect. A marker stores a buffer and a location within
that buffer, but it isn't itself located in a buffer.
> 3. When we document `char-after', we don't say
> that the char (which is conceptually _in_ the
> buffer) "points at" a buffer position. We
> say "Return the character _in_ current buffer
> _at_ position POS."
>
> Markers, like characters, are at buffer
> positions (chars are actually after, not at).
See above: that's correct about characters, but incorrect about
markers.
> This is how we treat overlays.
Overlays are completely different beasts.
next prev parent reply other threads:[~2019-11-08 19:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 21:26 bug#38051: 26.3; (elisp) `Insertion' use of verb "point" Drew Adams
2019-11-04 17:23 ` Eli Zaretskii
2019-11-08 0:36 ` Stefan Kangas
2019-11-08 17:53 ` Drew Adams
2019-11-08 19:11 ` Eli Zaretskii [this message]
[not found] <<10c2ca80-b3d5-4efb-a2b1-5ded0cc8a14d@default>
[not found] ` <<83sgn3h7yj.fsf@gnu.org>
2019-11-04 18:10 ` Drew Adams
2019-11-04 18:36 ` Eli Zaretskii
[not found] ` <<874kzfyzk5.fsf@marxist.se>
[not found] ` <<3b0f7464-a74f-4687-b91b-b654697cc1cc@default>
[not found] ` <<83a796b2tx.fsf@gnu.org>
2019-11-08 19:56 ` Drew Adams
2019-11-08 20:14 ` Eli Zaretskii
2019-11-09 14:55 ` Stefan Kangas
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=83a796b2tx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=38051@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=stefan@marxist.se \
/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).