unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r117969: Font-lock `cl-flet*', too.
Date: Sun, 28 Sep 2014 15:41:13 +0200	[thread overview]
Message-ID: <87bnpz981y.fsf@zigzag.favinet> (raw)
In-Reply-To: <m3oau017t9.fsf@gmail.com> (Leo Liu's message of "Sun, 28 Sep 2014 16:13:38 +0800")

[-- Attachment #1: Type: text/plain, Size: 978 bytes --]

() Leo Liu <sdl.web@gmail.com>
() Sun, 28 Sep 2014 16:13:38 +0800

   I noted this problem some time ago but decided not to fontify
   it so that this nonstandard macro doesn't get much use.

It's hard to judge the efficacy of such subtle negative feedback.

   cl-flet* should probably be removed. Common lisp doesn't have
   this macro. Personally I prefer cl-labels when needing
   something like cl-flet*.

Thanks for the tip (i am ignorant of most things Common Lisp).
I think until the time ‘cl-flet*’ is truly removed from Emacs,
there is no harm in it being fontified like the others, but if
you think otherwise and are willing to start the process for its
eventual removal, feel free to revert the change.

[cc added]

-- 
Thien-Thi Nguyen
   GPG key: 4C807502
   (if you're human and you know it)
      read my lisp: (responsep (questions 'technical)
                               (not (via 'mailing-list)))
                     => nil

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

       reply	other threads:[~2014-09-28 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1XY9Oa-0006fM-Vf@vcs.savannah.gnu.org>
     [not found] ` <m3oau017t9.fsf@gmail.com>
2014-09-28 13:41   ` Thien-Thi Nguyen [this message]
2014-09-28 16:41     ` trunk r117969: Font-lock `cl-flet*', too Stefan Monnier
2014-09-28 23:09       ` Leo Liu
2014-09-29  1:30         ` Stefan Monnier
2014-09-29  6:41           ` Leo Liu
2014-09-29  7:13             ` Leo Liu
2014-09-29 13:15             ` Stefan Monnier

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=87bnpz981y.fsf@zigzag.favinet \
    --to=ttn@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@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 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).