unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tim Johnson <tim@akwebsoft.com>
To: Drew Adams <drew.adams@oracle.com>, MLEmacs <Help-gnu-emacs@gnu.org>
Subject: Re: [External] : dired+ warning
Date: Sat, 26 Nov 2022 11:08:00 -0900	[thread overview]
Message-ID: <bf7a1206-877f-651f-fd68-73bf8ba1e67e@akwebsoft.com> (raw)
In-Reply-To: <SJ0PR10MB5488D63CE8FAC13B08DF8691F3119@SJ0PR10MB5488.namprd10.prod.outlook.com>

On 11/25/22 3:17 PM, Drew Adams wrote:
>> 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.
Thanks Drew!

-- 
Tim
tj49.com




      parent reply	other threads:[~2022-11-26 20:08 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 ` [External] : " Drew Adams
2022-11-26 14:56   ` Emanuel Berg
2022-11-26 15:57     ` Drew Adams
2022-11-26 20:08   ` Tim Johnson [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=bf7a1206-877f-651f-fd68-73bf8ba1e67e@akwebsoft.com \
    --to=tim@akwebsoft.com \
    --cc=Help-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.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.
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).