unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Colascione <dancol@dancol.org>,
	emacs-devel <emacs-devel@gnu.org>, Tassilo Horn <tsdh@gnu.org>
Subject: Re: [Emacs-diffs] master 51e7e46: Font-lock elisp macros/special forms dynamically
Date: Sun, 15 Mar 2015 22:35:03 -0300	[thread overview]
Message-ID: <CAAdUY-L=wk_DVteHCMTr4KRkMCjqNH9mBEdcXmbMUx+twHSqtA@mail.gmail.com> (raw)
In-Reply-To: <jwvbnjuaxbm.fsf-monnier+emacs@gnu.org>

My initial reaction was the same as Drew, I was surprised at seing
this implemented without previous discussion. However...


I'm testing this change now and I like it! Of course there needs to be
a way for macros do declare themselves non-special. But I think being
special by default is a good choice.

I also vote for enabling this by default. Disabling an unwanted
feature is 100 times easier than discovering an unknown feature, for
newbies and veterans alike.

Finally, I'm positively surprised at how fast the update function is.
I would have expected some lag, but haven't found any (even though I'm
looking).

2015-03-15 16:15 GMT-03:00 Stefan Monnier <monnier@iro.umontreal.ca>:
>> Is it really a good idea to highlight *all* macros? Many are meant to be
>> used just like functions and have the same semantics.
>
> IMNSHO most of those are mistakes (should use compiler-macros instead).
>
>> Instead of updating a big macro regexp after load, there should be
>> a `declare' attribute that would let specific macros (and functions)
>> opt into being fontified specially.
>
> Maybe the other way around would be better: add a declaration that says
> "this macro faithfully mimicks the behavior of a function".
>
>> As it is, I'm going to have to disable this functionality locally.
>
> I must admit I haven't tried it out yet, so I'm not sure if I'll like
> the result.
>
>
>         Stefan
>



  reply	other threads:[~2015-03-16  1:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150315082509.21193.18465@vcs.savannah.gnu.org>
     [not found] ` <E1YX3rB-0005WV-PA@vcs.savannah.gnu.org>
2015-03-15  9:12   ` [Emacs-diffs] master 51e7e46: Font-lock elisp macros/special forms dynamically Daniel Colascione
2015-03-15 15:11     ` Artur Malabarba
2015-03-15 17:20     ` Drew Adams
2015-03-15 19:15     ` Stefan Monnier
2015-03-16  1:35       ` Artur Malabarba [this message]
2015-03-16  3:07         ` Stefan Monnier
2015-03-16  7:07           ` Tassilo Horn
2015-03-16  7:10             ` Daniel Colascione
2015-03-16  7:54               ` Tassilo Horn
2015-03-16  9:36                 ` Tassilo Horn
2015-03-16 12:58               ` Stefan Monnier
2015-03-16 14:47                 ` Tassilo Horn
2015-03-16 17:31                   ` Stefan Monnier
2015-03-16 20:26                     ` Tassilo Horn
2015-03-16 20:39                       ` Daniel Colascione
2015-03-16 20:56                         ` Stefan Monnier
2015-03-17  9:36                           ` Tassilo Horn
2015-03-17 10:17                             ` Artur Malabarba
2015-03-17 16:34                             ` Stefan Monnier
2015-03-17 16:47                               ` Nicolas Richard
2015-03-18  7:17                               ` Tassilo Horn
2015-03-18  9:10                                 ` Artur Malabarba
2015-03-18  9:20                                   ` Dmitry Gutov
2015-03-18 13:13                                 ` Stefan Monnier
2015-03-18 16:12                                   ` Tassilo Horn
2015-03-18 16:44                                     ` Stefan Monnier
2015-03-16 12:56             ` Stefan Monnier
2015-03-16  7:41       ` Tassilo Horn
2015-03-16 12:59         ` Stefan Monnier
2015-03-16 14:23           ` Artur Malabarba
2015-03-15 15:09   ` Artur Malabarba
2015-03-16  6:40     ` [Emacs-diffs] " Tassilo Horn

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='CAAdUY-L=wk_DVteHCMTr4KRkMCjqNH9mBEdcXmbMUx+twHSqtA@mail.gmail.com' \
    --to=bruce.connor.am@gmail.com \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=tsdh@gnu.org \
    /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).