From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: larsi@gnus.org, contovob@tcd.ie, emacs-devel@gnu.org
Subject: Re: Searching for line beginning
Date: Wed, 17 Aug 2022 14:48:30 +0300 [thread overview]
Message-ID: <838rnndrap.fsf@gnu.org> (raw)
In-Reply-To: <E1oO97W-00088B-V7@fencepost.gnu.org> (message from Richard Stallman on Tue, 16 Aug 2022 22:49:26 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: larsi@gnus.org, contovob@tcd.ie, emacs-devel@gnu.org
> Date: Tue, 16 Aug 2022 22:49:26 -0400
>
> > > If we want to fix this, I think we should just introduce two new
> > > functions for "real" bol/eol, because this is already awkward enough.
>
> > I won't object.
>
> What would these new functions do? How would they be different from
> bolp and eolp?
bolp and eolp don't _search_ for next/previous newline, they just
report if point already _is_ at or before a newline.
The intent is to have a function similar to line-beginning-position,
but without the stuff that accounts for fields.
next prev parent reply other threads:[~2022-08-17 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 15:43 Searching for line beginning Eli Zaretskii
2022-08-13 16:20 ` Stefan Monnier
2022-08-13 17:58 ` Eli Zaretskii
2022-08-14 12:54 ` Eli Zaretskii
2022-08-14 15:33 ` Basil L. Contovounesios
2022-08-14 15:36 ` Eli Zaretskii
2022-08-14 15:43 ` Lars Ingebrigtsen
2022-08-14 15:48 ` Eli Zaretskii
2022-08-15 4:28 ` Lars Ingebrigtsen
2022-08-15 11:29 ` Eli Zaretskii
2022-08-15 11:37 ` Lars Ingebrigtsen
2022-08-15 12:00 ` Eli Zaretskii
2022-08-17 2:49 ` Richard Stallman
2022-08-17 10:41 ` Lars Ingebrigtsen
2022-08-17 11:48 ` Eli Zaretskii [this message]
2022-08-17 11:52 ` Stefan Monnier
2022-08-18 12:37 ` Lars Ingebrigtsen
2022-08-14 17:24 ` Stefan Monnier
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=838rnndrap.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.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).