From: Drew Adams <drew.adams@oracle.com>
To: Tim Johnson <tim@akwebsoft.com>, MLEmacs <Help-gnu-emacs@gnu.org>
Subject: RE: [External] : dired+ warning
Date: Sat, 26 Nov 2022 00:17:06 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488D63CE8FAC13B08DF8691F3119@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <a7a9801a-2ab4-e7b4-d999-d65e38f0e3c8@akwebsoft.com>
> on GNU Emacs 28.2 (build 2, x86_64-pc-linux-gnu,
> GTK+ Version 3.24.20, cairo version 1.16.0)
> I get the following message:
>
> .emacs.d/elisp/dired+.el: Warning: ‘case’ is an
> obsolete alias (as of 27.1); use ‘cl-case’ instead.
> [5 times]
>
> I'm retired and use emacs just on occasion. I don't think
> this is a big deal, but I know that Drew is always on top
> of changes, so I thought I would mention it.
Hi Tim,
Congratulations on your retirement!
You should be able to ignore that warning, for now
at least. I think you could also put something
like this in your init file to suppress it, if you
care to: (defalias 'case 'cl-case)
(Same thing, BTW, for others of my libraries,
including Bookmark+, Info+, Isearch+, & Icicles.)
Many of my libraries work also for older Emacs
releases (see field "Compatibility" in the file
header's "Commentary"). Depending on which
release you use, you'll likely see byte-compiler
warnings about vars or functions not known to be
defined, or function invocations with the wrong
number of args. You can generally ignore such
warnings, which come from conditional code with
branches for different releases, etc.
next prev parent reply other threads:[~2022-11-26 0:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 22:27 dired+ warning Tim Johnson
2022-11-26 0:17 ` Drew Adams [this message]
2022-11-26 14:56 ` [External] : " Emanuel Berg
2022-11-26 15:57 ` Drew Adams
2022-11-26 20:08 ` Tim Johnson
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=SJ0PR10MB5488D63CE8FAC13B08DF8691F3119@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=tim@akwebsoft.com \
/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.