unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Spenser Truex <lists@spensertruex.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: Request: add cl-font-lock to Emacs or Elpa
Date: Sun, 15 Mar 2020 13:28:16 -0700	[thread overview]
Message-ID: <87v9n5747z.fsf@spensertruex.com> (raw)
In-Reply-To: <jwvpnddmx7i.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 15 Mar 2020 11:55:34 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> cl-font-lock is a package that does richer syntax highlighting for
>> Common Lisp. I'm the co-maintainer on it. We are interested in having it
>> included in Emacs or on Elpa. It is already on Melpa.
>>
>> https://github.com/cl-font-lock/cl-font-lock
>>
>> How can we move that along?
>
> Sorry, I saw the (title of the) message you sent a few weeks ago and put
> it into my "todo" but later removed it from my todo because I thought it
> had been handled by someone else (there was some commit soon afterwards
> that seemed related).

Thank you. I hope the package is simple enough to see what it is doing,
so that it can be added without issue.

I think it should be an opt-in feature, not a replacement for the
current syntax highlighting in lisp-mode because many users prefer the
old syntax highlighting. Also, it is not very sophisticated (it is just
regular expressions) and sometimes doesn't highlight right based on the
context.

The other issue with it is that it can't really be unloaded.

So if these issues are too great for it to be added then we will have to
fix them first.

>         Stefan

-- 
Spenser Truex
spensertruex.com
San Francisco, USA



  parent reply	other threads:[~2020-03-15 20:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15  6:58 Request: add cl-font-lock to Emacs or Elpa Spenser Truex
2020-03-15 14:31 ` Eli Zaretskii
2020-03-15 16:12   ` Stefan Monnier
     [not found] ` <jwvpnddmx7i.fsf-monnier+emacs@gnu.org>
2020-03-15 20:28   ` Spenser Truex [this message]
2020-03-15 20:57     ` Drew Adams
2020-03-17 17:32       ` Spenser
2020-03-17 17:43         ` Drew Adams
2020-03-17 18:13         ` Stefan Monnier
2020-03-17 18:25           ` Drew Adams
2020-03-17 18:42             ` Stefan Monnier
2020-03-19 13:56               ` YUE Daian
2020-03-19 14:19                 ` Stefan Monnier
2020-03-19 14:41                   ` YUE Daian
2020-03-19 17:15                     ` Stefan Monnier
2020-03-21  6:59                       ` YUE Daian
     [not found]           ` <87y2rtech3.fsf@spensertruex.com>
     [not found]             ` <jwvtv2hfm7a.fsf-monnier+emacs@gnu.org>
2020-03-21 22:40               ` Spenser Truex
2020-03-22 17:54                 ` Stefan Monnier
     [not found] <1F8693F6-6DD1-4D5A-A1B1-C38BCAD4977F@spensertruex.com>
2020-03-17 18:02 ` Spenser

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=87v9n5747z.fsf@spensertruex.com \
    --to=lists@spensertruex.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.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).