Re: source of `package cl is deprecated'

[Christopher Dimech <dimech@gmx.com>]

  (setq debug-on-error t)
   (setq debug-ignored-errors nil)
   (setq debug-on-message "unescaped character literals"))


---------------------
Christopher Dimech
General Administrator - Naiad Informatics - GNU Project (Geocomputation)
- Geophysical Simulation
- Geological Subsurface Mapping
- Disaster Preparedness and Mitigation
- Natural Resource Exploration and Production
- Free Software Advocacy


> Sent: Friday, December 04, 2020 at 9:46 PM
> From: "Omar Polo" <op@omarpolo.com>
> To: "Leo Butler" <leo.butler@umanitoba.ca>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: source of `package cl is deprecated'
>
> 
> 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.
> 
> HTH
> 
>