unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: More font-lock keywords for tcl.el
Date: Thu, 31 Mar 2005 15:36:56 -0500	[thread overview]
Message-ID: <jwv4qerimk0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <s9oeczsja4.fsf@xpc14.ast.cam.ac.uk> (Glenn Morris's message of "Thu, 31 Mar 2005 20:32:51 +0100")

>> Well, your patch distinguishes between tcl-keyword-list and
>> tcl-builtin-list, so is `namespace' more like `append' or more like
>> `if'? To me it feels more like an `if', in that it seems to be part
>> of the syntax rather than one of a set of builtin functions.
> It seems it can be used in a similar fashion to "proc", eg
>    namespace eval foo {
>       ... do stuff ...
>    }
> or like a simple command:
>    namespace import foo::*
> so IMO it could be either a builtin or keyword. I slightly prefer the
> former, but don't have an especially strong opinion.

I have no opinion at all, I was just asking because it seemed odd.
As mentioned originally, feel free to install whatever you feel is right.

> ii) be highlighted in some other face. keyword or builtin (?) seem to be
> the only non-obviously-wrong faces left.

There's no reason to restrict oneself to font-lock*-face faces.
It might be better to use `defface' to create a new face (which could just
inherit from font-lock-warning-face) so users who feel that \ shouldn't be
so "in your face" can change it without changing font-lock-warning-face.


        Stefan

      reply	other threads:[~2005-03-31 20:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-30 15:24 More font-lock keywords for tcl.el Glenn Morris
2005-03-30 16:20 ` Stefan Monnier
2005-03-30 17:33   ` Glenn Morris
2005-03-30 22:18     ` Stefan Monnier
2005-03-31 19:32       ` Glenn Morris
2005-03-31 20:36         ` Stefan Monnier [this message]

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=jwv4qerimk0.fsf-monnier+emacs@gnu.org \
    --to=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).