From: Christopher Dimech <dimech@gmx.com>
To: Omar Polo <op@omarpolo.com>
Cc: help-gnu-emacs@gnu.org, Leo Butler <leo.butler@umanitoba.ca>
Subject: Re: source of `package cl is deprecated'
Date: Fri, 4 Dec 2020 22:11:29 +0100 [thread overview]
Message-ID: <trinity-db4f1ed6-1cde-4b31-8592-ea012e01c111-1607116289871@3c-app-mailcom-bs04> (raw)
In-Reply-To: <87h7p1wb86.fsf@omarpolo.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
>
>
next prev parent reply other threads:[~2020-12-04 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 18:13 source of `package cl is deprecated' Leo Butler
2020-12-04 20:27 ` Eli Zaretskii
2020-12-04 23:21 ` Leo Butler
2020-12-04 20:36 ` Stefan Monnier
2020-12-04 20:46 ` Omar Polo
2020-12-04 21:11 ` Christopher Dimech [this message]
2020-12-04 21:30 ` Leo Butler
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=trinity-db4f1ed6-1cde-4b31-8592-ea012e01c111-1607116289871@3c-app-mailcom-bs04 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=leo.butler@umanitoba.ca \
--cc=op@omarpolo.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).