From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 57907@debbugs.gnu.org
Subject: bug#57907: 29.0.50; Using keywords with cl-loop
Date: Sun, 18 Sep 2022 15:01:05 +0200 [thread overview]
Message-ID: <m2sfko4z1q.fsf@Mini.fritz.box> (raw)
In-Reply-To: <87mtaw4zgh.fsf@posteo.net> (Philip Kaludercic's message of "Sun, 18 Sep 2022 12:52:14 +0000")
Philip Kaludercic <philipk@posteo.net> writes:
> Interesting, I did not know this. But the point remains that Common
> Lisp's loop accepts both the symbol "a" from the "COMMON-LISP" package
> and from the "KEYWORD" package, right?
Right, from any package. The reason is that otherwise one couldn't
write (loop repeat ...), for example, if a package defines its own
repeat symbol.
>> Wouldn't it be nice if Emacs finally decided to have Common Lisp packages?
>
> Yeah, if only we could convince Emacs to do that ;)
I could convince Emacs, amd I would even invest the effort doing this,
seriously.
But there are obstacles...
Hold on, I'm getting my popcorn out :-)
prev parent reply other threads:[~2022-09-18 13:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 12:03 bug#57907: 29.0.50; Using keywords with cl-loop Philip Kaludercic
2022-09-18 12:20 ` Lars Ingebrigtsen
2022-09-18 12:28 ` Philip Kaludercic
2022-09-18 12:37 ` Lars Ingebrigtsen
2022-09-18 12:46 ` Philip Kaludercic
2022-09-19 8:06 ` Lars Ingebrigtsen
2022-09-19 10:16 ` Philip Kaludercic
2022-09-19 12:52 ` Lars Ingebrigtsen
[not found] ` <handler.57907.B.166350264228653.ack@debbugs.gnu.org>
2022-09-18 12:26 ` bug#57907: Acknowledgement (29.0.50; Using keywords with cl-loop) Philip Kaludercic
2022-09-18 20:12 ` Philip Kaludercic
2022-09-18 12:38 ` bug#57907: 29.0.50; Using keywords with cl-loop Gerd Möllmann
2022-09-18 12:52 ` Philip Kaludercic
2022-09-18 13:01 ` Gerd Möllmann [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=m2sfko4z1q.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57907@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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.