Bug 335737 - Highlight system ignores "lookAhead" attribute when RegExpr contains placeholders
Summary: Highlight system ignores "lookAhead" attribute when RegExpr contains placeho...
Status: RESOLVED WORKSFORME
Alias: None
Product: kate
Classification: Applications
Component: syntax (other bugs)
Version First Reported In: 3.13.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-06-03 04:44 UTC by vadimuzzz
Modified: 2018-10-27 02:41 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vadimuzzz 2014-06-03 04:44:20 UTC
Highlight system ignores "lookAhead" attribute  when RegExpr contains placeholders. 
I found this in VHDL if it matters. 
Simple VHDL syntax file with placeholder in regex: http://paste.kde.org/pcnwuch06
Test file #1:  http://paste.kde.org/pqltrqwx7 (2nd line is not highlighted)
Test file #2:  http://paste.kde.org/pqltrqwx7 (2nd line is not highlighted, 3rd is highlighted)
Simple VHDL syntax file w/o placeholder in regex: http://paste.kde.org/pxc8i5xmt

Reproducible: Always

Steps to Reproduce:
1. Put vhdl.xml (see above) in ~/.kde4/share/apps/katepart/syntax 
2. Run kate or kwrite
3. Open test.vhd or test2.vhd
Actual Results:  
Looks like "lookAhead" attribute is ignored, but if you replace in "<RegExpr        attribute="Normal Text"     context="look_semicolon"  insensitive="true"  dynamic="true" lookAhead = "true" endRegion="entity_region"
                                String="\b(end(\s+entity)?)(\s+%1)?" />"
'%1' with '&varname;' both lines (2 and 3) in test file #2 are  correctly highlighted.


Expected Results:  
Correct highlighting of line 2 in test.vhd with vhdl.xml with '%1' in regex
Comment 1 Buovjaga 2016-06-19 12:20:23 UTC
Sadly the KDE pastes have disappeared :(
Could you upload the files as attachments so they won't ever expire?
Comment 2 Andrew Crouthamel 2018-09-26 22:23:23 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 02:41:36 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!