From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Thierry Volpiatto <thierry.volpiatto@gmail.com>
Cc: 15777@debbugs.gnu.org
Subject: bug#15777: 24.3.50; cl symbols are no more fontlocked
Date: Fri, 01 Nov 2013 15:22:25 -0400 [thread overview]
Message-ID: <jwvsivgoryh.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87vc0cuhag.fsf@gmail.com> (Thierry Volpiatto's message of "Fri, 01 Nov 2013 19:07:51 +0100")
> I am sorry, but moving to cl-lib is not trivial
Then we should try and reduce the effort needed. My experience with
converting most of Emacs's own code to use cl-lib was rather
straightforward: remove the (require 'cl), byte-compile, look at the
output for complaints about unknown functions, search&replace
those names.
> and a lot of applications are still using cl.
I know, which is why `cl' is still fully supported and will remain that
way for a little while.
> What you are discouraging is maintaining external elisp libraries,
> remember that many people are using emacs just because there is external
> libraries.
We're only talking about the color given to symbols like defun*
and loop. It doesn't seem like that should discourage
external libraries.
Stefan
PS: the set of macros that are highlighted could/should be determined
dynamically, so that your own local macros can also be highlighted with
the `keyword' face. I'd welcome a patch that does that, and most likely
such a patch would automatically highlight `loop' when cl.el is loaded.
next prev parent reply other threads:[~2013-11-01 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 6:51 bug#15777: 24.3.50; cl symbols are no more fontlocked Thierry Volpiatto
2013-11-01 12:58 ` Stefan Monnier
2013-11-01 15:19 ` Drew Adams
2013-11-01 18:07 ` Thierry Volpiatto
2013-11-01 19:22 ` Stefan Monnier [this message]
2013-11-01 19:33 ` Drew Adams
2013-11-02 9:01 ` Thierry Volpiatto
2013-11-02 15:11 ` Drew Adams
2013-11-03 1:04 ` Stefan Monnier
2013-11-03 6:32 ` Drew Adams
2016-06-26 16:39 ` Noam Postavsky
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvsivgoryh.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=15777@debbugs.gnu.org \
--cc=thierry.volpiatto@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.