Executing the following example code
(with-temp-buffer
(insert foo)
(setq font-lock-keywords '((foo . bold)))
(font-lock-fontify-keywords-region (point-min) (point-max)))
will result in an error that the variable `bold' is void. If you use,
for example, `font-lock-comment-face' instead of
You can always fix these problems locally by setting or binding
deactivate-mark in the particular place. WOuld you please fix it that
way?
Because I just compiled a fresh CVS checkout of Emacs and still see
the problem and haven't found a check-in by Stefan related to the
(setq font-lock-keywords '((foo . bold)))
This shouldn't be a face symbol but an expression (whose value is typically
a face symbol). I.e.:
(setq font-lock-keywords '((foo (0 'bold
-- Stefan
Title: E-mail message content
Bonjour,
Il semble que vous ne fassiez pas encore partie de notre club.
Voudriez vous en faire partie ? L'inscription est gratuite et vous pouvez en retirer des avantages financiers importants.
pour visiter notre site : Clicquez ici
avec nos remerciements pour
On Mar 27, 2005, at 9:50 AM, Stefan Monnier wrote:
I couldn't get your patch to work. However, I did see what was going
on
and I managed to write my own patch. I don't know if this could break
anything else, but it does fix my OS X completion problems.
Thanks, I'll install it later.
From my
I am seeing frequent (one per day or so), but not reliably repeatable emacs
crashes when I visit a new folder in mh-e.
I'm cannot spend time looking at a crash in a version built more than
six months ago...
Can you try an up-to-date version, and see if the problem has been
fixed
In article [EMAIL PROTECTED], Dave Love [EMAIL PROTECTED] writes:
Kenichi Handa [EMAIL PROTECTED] writes:
I don't know which coding systems should be utf-16 in that
environment. It seems that at least
default-file-coding-system should not be utf-16. Do you
know a precise recipe of
I do not know whether anything relies on this behavior, but before
making any incompatible change this close before a release, one would
better be really extra careful.
`read-directory-name' inherits its current behavior from `read-file-name'.
The Emacs manual says:
If DEFAULT is
I find the new display features concerning `escape-glyph' and
`show-nonbreak-escape' annoying, but also they're obscure and partly
inconsistent. This is roughly what I went through on encountering
them.
First you wonder why, say, ^L in your source files is apparently being
font-locked as a
On Mon, 28 Mar 2005 02:59:33 +0300, Juri Linkov [EMAIL PROTECTED] wrote:
I agree. ^L fontified as a keyword looks horrible. That's why I suggested
to change its color to dark red to look more like comments.
We already had this argument.
In other buffers I think that instead of adding escape
10 matches
Mail list logo
