all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <13755@debbugs.gnu.org>
Subject: bug#13755: 24.3.50; regression: incorrect font-lock highlighting
Date: Mon, 25 Feb 2013 22:16:21 -0800	[thread overview]
Message-ID: <CAD0E6FBE69B478FB112A12358BA630D@us.oracle.com> (raw)
In-Reply-To: <37407E4E6385422185BDB9337946D9F4@us.oracle.com>

> The build from 2013-02-17 broke not only whether/when font-locking
> occurs (see bugs #13751 and #13730).  It broke also what gets
> highlighted.  A build from Feb 15 shows no font-lock problems.
>  
> See the two attached screenshots.  The one from 02-17 does 
> not highlight the command name
> (`icicle-customize-apropos-options-of-type') 
> completely, as it should and as does the one from 02-15.

Let me add, in case it helps, that I use this code:

(font-lock-add-keywords
 'emacs-lisp-mode
 `((,(concat "(" (regexp-opt
                  '("icicle-define-add-to-alist-command"
                    "icicle-define-command"
                    "icicle-define-file-command"
                    "icicle-define-sort-command")
                  t)
             "\\>[ \t'\(]*\\(\\sw+\\)?")
    (1 font-lock-keyword-face)
    ;; Index (2 or 3) depends on whether or not shy groups are supported.
    ,(list (if (string-match "\\(?:\\)" "") 2 3)
           'font-lock-function-name-face nil t))
   ("(\\(icicle-condition-case-no-debug\\)\\>"
    1 font-lock-keyword-face)))






  reply	other threads:[~2013-02-26  6:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 22:38 bug#13755: 24.3.50; regression: incorrect font-lock highlighting Drew Adams
2013-02-26  6:16 ` Drew Adams [this message]
2013-03-09 15:52   ` Stefan Monnier
2013-03-09 17:16     ` Drew Adams
2013-03-10  5:39       ` Stefan Monnier
2013-03-10 17:16         ` Drew Adams
2013-03-09 14:38 ` Drew Adams

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=CAD0E6FBE69B478FB112A12358BA630D@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13755@debbugs.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.