unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Clément Pit--Claudel" <clement.pitclaudel@live.com>,
	24176@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#24176: Confusing interaction between define-derived-mode and font-lock-add-keywords
Date: Mon, 24 Jan 2022 11:56:18 +0100	[thread overview]
Message-ID: <87ilu91jxp.fsf@gnus.org> (raw)
In-Reply-To: <jwvo8xabaey.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 17 Nov 2019 13:55:49 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> Stefan, is this working as designed?
>
> Not really, no.  The design didn't take this into account at least.
>
>> If so, the behaviour should perhaps be mentioned in the doc for
>> font-lock-add-keywords and/or define-derived-mode?
>
> I think it'd be better to fix it ;-)

I think I've fixed this in Emacs 29.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-01-24 10:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-07  6:41 bug#24176: Confusing interaction between define-derived-mode and font-lock-add-keywords Clément Pit--Claudel
     [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 [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=87ilu91jxp.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=24176@debbugs.gnu.org \
    --cc=clement.pitclaudel@live.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=npostavs@users.sourceforge.net \
    /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).