From: Kyle Meyer <kyle@kyleam.com>
To: Michael Eliachevitch <m.eliachevitch@posteo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-contacts.el use lexical-let not defined in cl-lib
Date: Sat, 24 Apr 2021 01:05:37 -0400 [thread overview]
Message-ID: <87bla4gtlq.fsf@kyleam.com> (raw)
In-Reply-To: <87czul1e8p.fsf@posteo.de>
Michael Eliachevitch writes:
> Dear all,
>
> I'm not sure if this is the correct mailinglist for org-contrib
> bugs.
Thanks for the report. Yes, this is the place [*]. stardiviner (+cc)
recently took over maintaining org-contacts.el.
> I found that org-contacts.el uses `lexical-let*` which is defined in
> `cl`, but it only requires `cl-lib` where it is not defined.
[...]
> My org version is release_9.4.5-321-ge641d3. However, I see that
> on the master branch still uses lexical-let*.
>
> Is this a bug or some error in my configuration? Should I send an
> email elsewhere or submit a bug-report? Because (require 'cl) is
> deprecated, test solution would be to replace the lexical-let*
> with something else like a normal let*, but I'm not confident
> enough in my lisp to do this by myself.
This is a bug in org-contacts.el. Loading cl was dropped in ea238b78f
(contrib: move a few libraries to cl-lib in place of compile-time cl,
2015-11-06), and, as you note, it's still needed for lexical-let.
I haven't looked at the org-contact's lexical-let call sites closely,
but I think the way forward is to move org-contacts.el over to lexical
binding and stop using anything from cl.el.
stardiviner, what do you think?
[*] ... though sometime soon the plan is to move contrib/ packages
elsewhere, at which point I guess it mostly will depend on who is
taking care of a given contrib/ package.
https://orgmode.org/list/87wnzfy60h.fsf@bzg.fr
next prev parent reply other threads:[~2021-04-24 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 10:27 org-contacts.el use lexical-let not defined in cl-lib Michael Eliachevitch
2021-04-24 5:05 ` Kyle Meyer [this message]
2022-03-21 11:36 ` Christopher M. Miles
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bla4gtlq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=emacs-orgmode@gnu.org \
--cc=m.eliachevitch@posteo.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).