From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Elisp syntax hilighting problem
Date: Sun, 23 Apr 2006 10:05:22 -0400 [thread overview]
Message-ID: <873bg4xu9o.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <444975EF.8040805@student.lu.se> (Lennart Borgman's message of "Sat, 22 Apr 2006 02:16:47 +0200")
> The defconst below sometimes upset the syntax highlighting so that the
> function following it is in the same face as the string:
[...]
> More problems: The \\= is not marked. The two [ at beginning of line is
> marked with a red face.
The warning (red) face is used to warn you that this part of the code can
cause the problem you mention.
Stefan
prev parent reply other threads:[~2006-04-23 14:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-22 0:16 Elisp syntax hilighting problem Lennart Borgman
2006-04-22 15:13 ` Andreas Schwab
2006-04-22 23:22 ` Lennart Borgman
2006-04-23 14:05 ` 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=873bg4xu9o.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).