GNU bug report logs - #19882
25.0.50; Backwards font-lock regex in m4-mode

Previous Next

Full log

Message #13 received at control <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> gmail.com>
To: Marcin Borkowski <mbork <at> mbork.pl>
Cc: Rupert Swarbrick <ruperts <at> broadcom.com>, 19882 <at> debbugs.gnu.org
Subject: Re: bug#19882: 25.0.50; Backwards font-lock regex in m4-mode
Date: Tue, 05 Jun 2018 20:09:12 -0400

tags 19882 fixed
close 19882 25.1
quit

Marcin Borkowski <mbork <at> mbork.pl> writes:

> On 2015-02-16, at 11:32, Rupert Swarbrick <ruperts <at> broadcom.com> wrote:
>
>> In m4-mode.el, the last two sexps in m4-font-lock-keywords are the wrong
>> way around. As a result, if you are writing M4 code to be expanded in
>> "-P mode", so have things like
>>
>>   m4_define
>>
>> in the file, then the "define" part gets matched by the penultimate
>> regex, so m4_ doesn't get highlighted as part of a keyword.

> in case the problem is still there (I don't use m4, so it's difficult
> for me to verify it), would you be able to provide a patch now?

Seems to be fixed in 25 (I did M-x m4-mode and typed in m4_define).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.