From: Tino Calancha <tino.calancha@gmail.com>
To: Nicolas Petton <nicolas@petton.fr>
Cc: 25129@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#25129: 26.0.50; seq-some function
Date: Wed, 7 Dec 2016 19:31:41 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1612071928370.20428@calancha-pc> (raw)
In-Reply-To: <87eg1k5951.fsf@petton.fr>
On Wed, 7 Dec 2016, Nicolas Petton wrote:
> Tino Calancha <tino.calancha@gmail.com> writes:
>
>> Nicolas Petton <nicolas@petton.fr> writes:
>>
>>> Pierre Lorenzon <devel@pollock-nageoire.net> writes:
>>>
>>> Hi Pierre,
>>>
>>>> I well understand now that I must use seq-find instead of
>>>> seq-some but I think that I will not be the only one being
>>>> confused by these functions specifications !
>>>
>>> There is a mistake (extra if) in the documentation, I will fix that.
>>>
>>> Other than that, is the following less confusing?
>>>
>>> Return non-nil if PRED returns non-nil for at least one element of SEQUENCE.
>>> If so, return the value returned by PRED.
>
>> The previous doc string contains more information: it explicitely says
>> that it returns the _first_ non-nil (PRED element).
>
> Indeed, what about:
>
> Return non-nil if PRED returns non-nil for at least one element of SEQUENCE.
> If so, return the first non-nil value returned by PRED.
Yeah better.
The first line with the repetition of 'non-nil' sounds a little poetic.
How about?
Return non-nil if PRED is satisfied for at least one element of SEQUENCE.
If so, return the first non-nil value returned by PRED.
next prev parent reply other threads:[~2016-12-07 10:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 8:09 bug#25129: 26.0.50; seq-some function Pierre Lorenzon
2016-12-07 8:48 ` Nicolas Petton
2016-12-07 10:19 ` Tino Calancha
2016-12-07 10:24 ` Nicolas Petton
2016-12-07 10:31 ` Tino Calancha [this message]
2016-12-07 12:31 ` Nicolas Petton
2016-12-07 16:16 ` Eli Zaretskii
2016-12-07 16:57 ` Pierre Lorenzon
2016-12-07 16:28 ` Pierre Lorenzon
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=alpine.DEB.2.20.1612071928370.20428@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=25129@debbugs.gnu.org \
--cc=nicolas@petton.fr \
/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).