[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals
From: |
Alan Mackenzie |
Subject: |
bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals |
Date: |
Thu, 24 Jan 2013 22:16:04 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Hi, Glenn,
On Thu, Jan 24, 2013 at 01:28:33PM -0500, Glenn Morris wrote:
> Leo Liu wrote:
> > In an awk buffer having the following text:
> > #--BEGIN--
> > NF { /xyz/ }
> > NF {
> > /xyz/
> > }
> > #--END--
> > I have the second regexp properly font-locked but not the first one.
> Do you have an example of an actual useful awk script showing the issue,
> because this one seems like a pointless no-op?
This is a real bug, perhaps not a difficult one. "/regexp/" is an
expression with value 1 iff the current input line matches the regexp.
So a line like
NF { print /xyz/ }
is perfectly legitimate, printing 1 if there's an "xyz" on the line.
I'm looking at this bug at the moment.
--
Alan Mackenzie (Nuremberg, Germany).
- bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals, Leo Liu, 2013/01/24
- bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals, Glenn Morris, 2013/01/24
- bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals,
Alan Mackenzie <=
- bug#12274: 24.2; awk-mode indentation failure, Alan Mackenzie, 2013/01/25
- bug#12274: 24.2; awk-mode indentation failure, Glenn Morris, 2013/01/25
- bug#12274: 24.2; awk-mode indentation failure, Alan Mackenzie, 2013/01/25
- bug#12274: 24.2; awk-mode indentation failure, Stefan Monnier, 2013/01/26
bug#13541: 24.2.92; awk-mode: wrong font locking regexp literals, Alan Mackenzie, 2013/01/25