From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Virtual pet for Emacs
Date: Wed, 04 May 2022 22:14:28 -0400 [thread overview]
Message-ID: <jwv5ymkd8uj.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: m2pmktzg3l.fsf@me.com
> (defun points-to-evolution (total-points)
> (dolist (points +pet-evolution-tree+)
> (if (> (car points) total-points)
> (return ;; <------------------- HERE
> (nth 1
> (assoc (car points) +pet-evolution-tree+))))))
That should be `cl-dolist` and `cl-return`.
Stefan
next prev parent reply other threads:[~2022-05-05 2:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 3:25 Virtual pet for Emacs vidak
2022-04-26 9:08 ` Alex
2022-05-04 0:15 ` ~vidak
2022-05-04 0:20 ` Emanuel Berg
2022-05-04 1:14 ` ~vidak
2022-05-04 4:34 ` Emanuel Berg
2022-05-06 12:00 ` Alex
2022-05-04 11:34 ` Rudolf Adamkovič
2022-05-04 15:53 ` vidak
2022-05-04 18:36 ` Emanuel Berg
2022-05-04 18:35 ` Emanuel Berg
2022-05-05 2:14 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-05-05 3:19 ` Emanuel Berg
2022-05-05 3:47 ` Emanuel Berg
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=jwv5ymkd8uj.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).