From: Glenn Morris <rgm@gnu.org>
To: 53014-done@debbugs.gnu.org
Subject: bug#53014: 27.2; `cl-macs.el' no longer provides `cl-macs'
Date: Tue, 04 Jan 2022 20:28:58 -0500 [thread overview]
Message-ID: <d04k6jt1gl.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54886584F0E883D8E6D6D1EFF34A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Tue, 4 Jan 2022 21:14:08 +0000")
There are several misconceptions in this report.
cl-macs.el continues to provide cl-macs, as it always has done.
Loading internal sub-components of cl-lib has always been discouraged.
The way to use cl-lib continues to be to (require 'cl-lib).
Code needing only macros can add eval-when-compile to that.
This is documented in the usage node of the cl manual.
(This was explained 6 years ago in bug#22291.)
prev parent reply other threads:[~2022-01-05 1:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 21:14 bug#53014: 27.2; `cl-macs.el' no longer provides `cl-macs' Drew Adams
2022-01-05 1:28 ` Glenn Morris [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
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=d04k6jt1gl.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=53014-done@debbugs.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).