From: Nicolas Petton <nicolas@petton.fr>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 25129@debbugs.gnu.org, tino.calancha@gmail.com
Subject: bug#25129: 26.0.50; seq-some function
Date: Wed, 07 Dec 2016 11:24:58 +0100 [thread overview]
Message-ID: <87eg1k5951.fsf@petton.fr> (raw)
In-Reply-To: <87vauwghyb.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
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.
Cheers,
Nico
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2016-12-07 10:24 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 [this message]
2016-12-07 10:31 ` Tino Calancha
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eg1k5951.fsf@petton.fr \
--to=nicolas@petton.fr \
--cc=25129@debbugs.gnu.org \
--cc=tino.calancha@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 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.