Re: source of `package cl is deprecated'

[Leo Butler <leo.butler@umanitoba.ca>]

Omar Polo <op@omarpolo.com> writes:

> ********************************************************
> Caution: This message was sent from outside the University of Manitoba.
> ********************************************************
>
> Leo Butler <leo.butler@umanitoba.ca> writes:
>
>> I updated/upgraded my debian system this morning, which pulled in emacs
>> 27.1.
>>
>> A number of my home-rolled emacs extensions relied on cl; I have
>> migrated them to cl-lib, but there is an extension that is still causing
>> emacs to emit the above-mentioned warning on start-up (and when run with
>> --daemon, emacs halts and must be killed, which I guess is a bug).
>>
>> Question: how do I trace/find the offending bit of code? Ideally, I
>> would like to be able to force an error and use the debugger, but I
>> can't figure out how to do that.
>>
>> TIA,
>> Leo
>
> You can find which files depends on cl using something like this IIRC
>
>     (require 'loadhist)
>     (file-dependents (feature-file 'cl))
>
> Anyway, using cl shouldn’t cause emacs to hang, so that must be a
> separate bug.

Thank you for the suggestion.

I found that suggestion on stackexchange and I tried it, but it is
uninformative. In my current emacs, I find that slime is a problem:

==> ("/usr/share/emacs/site-lisp/elpa/slime-2.24/contrib/slime-repl.el"
"/usr/share/emacs/site-lisp/elpa/slime-2.24/contrib/bridge.el" 
"/usr/share/emacs/site-lisp/elpa/slime-2.24/contrib/slime-presentations.el")

The problem is that the home-rolled extension that causes emacs to emit
the deprecation message is unrelated to slime.

I know the file which is the proximate cause of the problem, I simply
cannot find the ultimate source (i.e. the offending line of code).

Am I missing something obvious?

Leo