unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit--Claudel" <clement.pitclaudel@live.com>
To: 24176@debbugs.gnu.org
Subject: bug#24176: Confusing interaction between define-derived-mode and font-lock-add-keywords
Date: Sun, 7 Aug 2016 02:41:30 -0400	[thread overview]
Message-ID: <1b9e5891-9843-a9d7-c29f-7b9544a72a12@live.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 686 bytes --]

Hi bug-gnu-emacs,

Given the following mode definitions, I was expecting ~/a to have one keyword, ~/b to have two, and ~/c to have three:

(define-derived-mode ~/a fundamental-mode
  (font-lock-add-keywords nil `(("a" 0 'font-lock-keyword-face))))
(define-derived-mode ~/b ~/a
  (font-lock-add-keywords nil `(("b" 0 'font-lock-builtin-face))))
(define-derived-mode ~/c ~/b
  (font-lock-add-keywords nil `(("c" 0 'font-lock-constant-face))))

This assumption is wrong, as can be easily verified by opening a new buffer, inserting "abc", and switching between ~/a, ~/b, ~/c.

What's going on? Is this a font-lock bug, a doc bug, or a user-got-confused issue?

Clément.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-08-07  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07  6:41 Clément Pit--Claudel [this message]
     [not found] ` <handler.24176.B.14705521086608.ack@debbugs.gnu.org>
2016-08-07  6:57   ` bug#24176: Acknowledgement (Confusing interaction between define-derived-mode and font-lock-add-keywords) Clément Pit--Claudel
2016-08-25  0:53     ` bug#24176: Confusing interaction between define-derived-mode and font-lock-add-keywords npostavs
2019-11-17  6:59       ` Lars Ingebrigtsen
2019-11-17 18:55         ` Stefan Monnier
2022-01-24 10:56           ` Lars Ingebrigtsen

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=1b9e5891-9843-a9d7-c29f-7b9544a72a12@live.com \
    --to=clement.pitclaudel@live.com \
    --cc=24176@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 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).