all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: how is emacs lisp syntax colored in emacs-lisp-mode?
Date: Tue, 10 Mar 2009 05:45:03 -0700 (PDT)	[thread overview]
Message-ID: <d745358e-b362-4890-b392-cc7d6b1bfe0f@e1g2000pra.googlegroups.com> (raw)

when coding elisp, lately i find myself using camelCase style for my
own function and variable names. Because i find that easier to
distinguish from built-in function/var/keywords.

on thinking about this, i thought it would not be necessary if emacs-
lisp-mode would just color all built in functions and variables.
However, the way it is syntax colored seems strange, unlike in most
major modes for langs where each class of keywords gets one color.

for example, these keywords would be colored purple by default:

 defun, lambda, while, if, progn, save-restriction, ...

while the following built-in keywords are uncolored (black):
narrow-to-region, mapc, goto-char, point-min, search-forward, car,
nil, replace-match ... etc.

is there a principle of how the keywords are colored?

thanks

  Xah
∑ http://xahlee.org/

             reply	other threads:[~2009-03-10 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10 12:45 Xah Lee [this message]
2009-03-10 13:43 ` how is emacs lisp syntax colored in emacs-lisp-mode? Tassilo Horn
2009-03-10 20:59   ` Xah Lee
2009-03-10 22:01     ` W Dan Meyer
2009-03-10 20:06 ` Nikolaj Schumacher
2009-03-11 17:51   ` Johan Bockgård
     [not found] ` <mailman.2878.1237105097.31690.help-gnu-emacs@gnu.org>
2009-03-16 23:54   ` Xah Lee
2009-03-17  2:41     ` Xah Lee
2009-03-17  8:41     ` Nikolaj Schumacher
     [not found]     ` <mailman.3385.1237279326.31690.help-gnu-emacs@gnu.org>
2009-03-17  9:53       ` Xah Lee

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=d745358e-b362-4890-b392-cc7d6b1bfe0f@e1g2000pra.googlegroups.com \
    --to=xahlee@gmail.com \
    --cc=help-gnu-emacs@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 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.