From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Testing whether a list contains at least one non-nil element
Date: Thu, 27 Oct 2022 06:01:12 +0200 [thread overview]
Message-ID: <87y1t1rk3b.fsf@dataswamp.org> (raw)
In-Reply-To: Y1mC3q9WltIgM4o5@protected.localdomain
Jean Louis wrote:
> cl- is Common Lisp prefix to conform those people who are
> used to Common Lisp. Those functions are bloated.
The are useful (and neat), that's why people use them, not
that they are used to them from CL.
But that's a possibility and correct for some people, and why
not? They were useful there, implemented here for that reason,
and after that they have been useful here as well. This is
completely natural, it's a good thing and it happens all
the time, God willing that will continue.
So if some dude comes up with something in some other Lisp
dialect first thing we should do after finishing the morning
milk and flakes is see if we could do that same thing here as
well so we also benefit from his ingenuity and overall just
elevate our game any and all ways possible ...
> (defun list-has-non-nil-p (list)
> "Test if list has non nil element."
> (elt (remq nil list) 0))
-1
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-10-27 4:01 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 10:16 Testing whether a list contains at least one non-nil element Heime
2022-10-25 10:46 ` Jean Louis
2022-10-25 10:47 ` Jean Louis
2022-10-25 10:50 ` Jean Louis
2022-10-25 12:12 ` Emanuel Berg
2022-10-26 18:56 ` Jean Louis
2022-10-27 3:54 ` [External] : " Drew Adams
2022-10-27 4:53 ` Jean Louis
2022-10-27 5:30 ` Emanuel Berg
2022-10-27 15:54 ` Drew Adams
2022-10-27 17:47 ` Elisp and CL (was: Re: [External] : Re: Testing whether a list contains at least one non-nil element) Emanuel Berg
2022-10-27 20:38 ` [External] : Re: Testing whether a list contains at least one non-nil element Jean Louis
2022-10-28 0:22 ` Emanuel Berg
2022-10-28 4:48 ` tomas
2022-10-28 5:19 ` Jean Louis
2022-10-28 6:20 ` Michael Heerdegen
2022-10-28 13:09 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-29 6:10 ` Michael Heerdegen
2022-10-29 15:25 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-10-30 12:49 ` Emanuel Berg
2022-10-29 6:38 ` tomas
2022-10-30 12:48 ` Emanuel Berg
2022-10-29 9:20 ` Emanuel Berg
2022-10-29 9:19 ` Emanuel Berg
2022-10-27 4:01 ` Emanuel Berg [this message]
2022-10-25 12:05 ` Michael Heerdegen
2022-10-25 12:15 ` Emanuel Berg
2022-10-25 15:59 ` [External] : " Drew Adams
2022-10-25 17:44 ` Emanuel Berg
2022-10-26 15:39 ` Drew Adams
2022-10-26 17:43 ` Emanuel Berg
2022-10-25 17:25 ` Joost Kremers
2022-10-25 17:51 ` Emanuel Berg
2022-10-25 19:44 ` Heime
2022-10-25 20:08 ` Joost Kremers
2022-10-25 20:15 ` [External] : " Drew Adams
2022-10-25 20:19 ` Joost Kremers
2022-10-26 3:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=87y1t1rk3b.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@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.
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).