unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefankangas@gmail.com>
Cc: "larsi@gnus.org" <larsi@gnus.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: master f117b5df4d: Add new functions eol and bol
Date: Fri, 19 Aug 2022 16:24:24 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488D5B2C845BA4742A85516F36C9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83r11ce3e3.fsf@gnu.org>

> How about position-at-bol or pos-at-bol?
> 
> (IMO, it's confusing to talk about "point at SOMEWHERE" because that's
> not how we use the term "point", except in the context of describing
> point's position.)

<nitpick>

+1. `position-at-...' makes sense, and
`point-at...' does not.

Point is the _current_ cursor position in some
buffer.  And window point is the cursor position
for the buffer displayed in some window.

The names `point-min|max' are legacy.  No need
to change them to `position-min|max'.  But they
shouldn't be used as a precedent for starting
to name position variables and functions with
"point" instead of "position" (or "pos").
___

(Separate point (!), but related: we shouldn't
talk about the "position of point".  Point _is_
a position - the position of the cursor.

E.g., +1 for Eli's point (!) here, but not for
speaking of "point's position", which just means
the _position of the position_ of the cursor.)

</nitpick>



  parent reply	other threads:[~2022-08-19 16:24 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166091536530.20326.14174671546998200051@vcs2.savannah.gnu.org>
     [not found] ` <20220819132245.AE2BBC0088A@vcs2.savannah.gnu.org>
2022-08-19 13:25   ` master f117b5df4d: Add new functions eol and bol Lars Ingebrigtsen
2022-08-19 13:34     ` Stefan Monnier
2022-08-19 13:36       ` Lars Ingebrigtsen
2022-08-19 21:02         ` Stefan Monnier
2022-08-19 21:24           ` Lars Ingebrigtsen
2022-08-19 13:55     ` Stefan Kangas
2022-08-19 14:04       ` Eli Zaretskii
2022-08-19 14:14         ` Robert Pluim
2022-08-19 14:56         ` Lars Ingebrigtsen
2022-08-19 16:24         ` Drew Adams [this message]
2022-08-19 21:42           ` [External] : " Tim Cross
2022-08-19 21:03         ` Stefan Monnier
2022-08-19 21:26           ` Lars Ingebrigtsen
2022-08-20 16:28             ` Gregory Heytings
2022-08-19 14:08       ` Lars Ingebrigtsen
2022-08-19 16:00         ` Stefan Kangas
2022-08-19 21:49           ` Lars Ingebrigtsen
2022-08-20  6:21             ` Eli Zaretskii
2022-08-20 16:47             ` Stefan Monnier
2022-08-21 16:19             ` Stefan Kangas
2022-08-22 10:03               ` Lars Ingebrigtsen
2022-08-23  3:05                 ` Stefan Kangas
2022-08-23  3:52                   ` Po Lu
2022-08-23 13:12                     ` Stefan Monnier
2022-08-24  3:53                       ` Richard Stallman
2022-08-24  4:28                         ` Po Lu
2022-08-24 11:58                         ` Stefan Monnier
2022-08-20  8:12       ` Po Lu
2022-08-20  9:22         ` Lars Ingebrigtsen
2022-08-20 11:37           ` Po Lu
2022-08-20 13:00             ` Lars Ingebrigtsen
2022-08-20 13:26               ` Po Lu
2022-08-19 22:15     ` Dmitry Gutov
2022-08-20  7:33       ` Lars Ingebrigtsen
2022-08-20  7:43         ` Eli Zaretskii
2022-08-20  9:21           ` Lars Ingebrigtsen
2022-08-20 16:46         ` Gregory Heytings
2022-08-20 16:49         ` Stefan Monnier
2022-08-20 17:14           ` Stefan Kangas
2022-08-21 12:01             ` Lars Ingebrigtsen
2022-08-20 18:46         ` Dmitry Gutov
2022-08-20 21:02           ` [External] : " Drew Adams

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=SJ0PR10MB5488D5B2C845BA4742A85516F36C9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=stefankangas@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.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).