all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gerard Vermeulen <gerard.vermeulen@posteo.net>
Cc: 71879@debbugs.gnu.org
Subject: bug#71879: 30.0.60; Docstring error in NOERROR argument part of re-search-forward
Date: Mon, 01 Jul 2024 20:30:12 +0300	[thread overview]
Message-ID: <86plrxdnq3.fsf@gnu.org> (raw)
In-Reply-To: <cadc7a71aa7f16ab729cffaf8fd1d1f2@posteo.net> (message from Gerard Vermeulen on Mon, 01 Jul 2024 16:13:38 +0000)

> Date: Mon, 01 Jul 2024 16:13:38 +0000
> From: Gerard Vermeulen <gerard.vermeulen@posteo.net>
> 
> Hello,
> 
> The last "if" clause in the NOERROR part of the re-search-forward 
> docstring
> is wrong.
> 
> It reads "if it is neither nil nor t, move to the limit of search and 
> return nil."
> 
> but if NOERROR equals neither nil nor t re-search-forward returns
> the start position of the match (when found) or nil (when no match
> found).

The full text of that part is as follows:

  The optional third argument NOERROR indicates how errors are handled
    when the search fails.  If it is nil or omitted, emit an error; if
    it is t, simply return nil and do nothing; if it is neither nil nor
    t, move to the limit of search and return nil.

Note the first sentence of the paragraph: this entire paragraph
describes how NOERROR affects the case when the search _fails_.  Thus,
the situation where the search succeeds is not relevant to the above
part of the doc string.

So I think this text is accurate and correct.

> By the way: using the-the finds a duplication "is is" in the NEWS
> file but I am unsure whether this merits a bug report.

Fixed, thanks.





  reply	other threads:[~2024-07-01 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 16:13 bug#71879: 30.0.60; Docstring error in NOERROR argument part of re-search-forward Gerard Vermeulen
2024-07-01 17:30 ` Eli Zaretskii [this message]
2024-07-01 17:48   ` Gerard Vermeulen
2024-07-13 10:23     ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=86plrxdnq3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71879@debbugs.gnu.org \
    --cc=gerard.vermeulen@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.