From: Pierre Lorenzon <devel@pollock-nageoire.net>
To: nicolas@petton.fr
Cc: 25129@debbugs.gnu.org
Subject: bug#25129: 26.0.50; seq-some function
Date: Wed, 07 Dec 2016 17:28:42 +0100 (CET) [thread overview]
Message-ID: <20161207.172842.539369297027198559.devel@pollock-nageoire.net> (raw)
In-Reply-To: <87h96g5dlu.fsf@petton.fr>
From: Nicolas Petton <nicolas@petton.fr>
Subject: Re: bug#25129: 26.0.50; seq-some function
Date: Wed, 07 Dec 2016 09:48:29 +0100
> 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.
Good !
>
> 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.
Yes this is absolutely clear now from my point of view.
I know taht this function has been first called seq-some-p
then seq-(some and its spec has maybe changed as well. But
now with your new documentation I htink that documentation
fit function behavior. That's only what we need. The fact
that function fit our own need is another question : in
fact seq-find does !
Thanks !
Pierre
>
> Cheers,
> Nico
prev parent reply other threads:[~2016-12-07 16:28 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
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 [this message]
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=20161207.172842.539369297027198559.devel@pollock-nageoire.net \
--to=devel@pollock-nageoire.net \
--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 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.