From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 14099@debbugs.gnu.org
Subject: bug#14099: 24.3.50; regression: bad font locking for `abort' in Lisp mode
Date: Sun, 31 Mar 2013 07:29:46 -0700 [thread overview]
Message-ID: <AB911A831DE3414BAE51809B744495E5@us.oracle.com> (raw)
In-Reply-To: <838v543zcr.fsf@gnu.org>
> > emacs -Q
> > Type this in an Emacs Lisp buffer:
> > (abort-recursive-edit)
> > Emacs now highlights `abort' here, which is bad.
>
> I can't reproduce this, but maybe I didn't do everything needed for
> reproduction. What exactly do you mean by "in an Emacs Lisp buffer"?
> How did you create such a buffer, starting from "emacs -Q"?
>
> What I did was to create a buffer and manually put it under
> emacs-lisp-mode.
The regression was apparently fixed. It is easy to repro it in the build I
reported on, from 2013-03-23. But it no longer repros in a build from 3-28.
As for reproducing in 3-23, just put that sexp in *scratch* (Lisp interaction
mode) or any buffer that is `emacs-lisp-mode'.
So you can close this bug (or I will), unless you want to investigate further
for some reason. I don't know what other changes were made when the regression
was introduced. This is a pretty basic mistake, so maybe the changes are worth
looking at.
Also, as I mentioned, I found no `abort' function etc. in Emacs, and even with
the latest build (abort) still highlights in red. What was fixed is that
(abort-recursive-edit) no longer has the `abort' part in red. But what is this
`abort' function, and why is it highlighted with `font-lock-warning-face'?
next prev parent reply other threads:[~2013-03-31 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-30 21:20 bug#14099: 24.3.50; regression: bad font locking for `abort' in Lisp mode Drew Adams
2013-03-31 5:36 ` Eli Zaretskii
2013-03-31 14:29 ` Drew Adams [this message]
2013-03-31 19:13 ` Drew Adams
2013-03-31 20:00 ` Eli Zaretskii
2013-03-31 21:01 ` Drew Adams
2013-04-03 17:50 ` Stefan Monnier
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=AB911A831DE3414BAE51809B744495E5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=14099@debbugs.gnu.org \
--cc=eliz@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).