unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	 Dmitry Gutov <dgutov@yandex.ru>,
	 emacs-devel@gnu.org
Subject: Re: master f117b5df4d: Add new functions eol and bol
Date: Sun, 21 Aug 2022 14:01:16 +0200	[thread overview]
Message-ID: <874jy5olf7.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmmD7yrk_Om5Yts=g-_0EZ7uoZBBLYQ=ap7BcStsmPyRGQ@mail.gmail.com> (Stefan Kangas's message of "Sat, 20 Aug 2022 10:14:24 -0700")

Stefan Kangas <stefankangas@gmail.com> writes:

>> I like using the `pos-` prefix.
>
> Using a prefix is more discoverable than a postfix: you can find all
> functions by saying, e.g., `C-h f pos TAB'.  So I'd prefer that.

So I think the votes are in, and `pos-eol' seems to be the winner.

I don't think the "-at" is necessary -- I mean, from a grammatical point
of view, it's better, but I don't think it makes the code clearer,
especially in the presence of the `point-min' and `point-max' work
horses.  (And it adds confusability with `point-at-eol'.)

So I think we'll go with `pos-eol', and I'm adjusting the code in that
direction now.



  reply	other threads:[~2022-08-21 12:01 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         ` [External] : " Drew Adams
2022-08-19 21:42           ` 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 [this message]
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=874jy5olf7.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --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).