https://bugs.kde.org/show_bug.cgi?id=405903

Nibaldo G. <nibg...@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Latest Commit|                            |https://commits.kde.org/syn
                   |                            |tax-highlighting/b518dcc648
                   |                            |6a4dc23785c2d53ae339a9d327e
                   |                            |546
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED

--- Comment #3 from Nibaldo G. <nibg...@gmail.com> ---
Git commit b518dcc6486a4dc23785c2d53ae339a9d327e546 by Nibaldo González.
Committed on 02/04/2019 at 05:21.
Pushed by ngonzalez into branch 'master'.

Allow line end context switches in empty lines

Summary:

### Bug: Don't skip empty lines after matching a LineContinue rule:

When you write an empty line after a line continuation character, the empty
lines are ignored.
This generates an incorrect highlight, since it includes within the context
multiple lines after a line continuation character, when the respective context
has `lineEndContext="#pop"`.

{F6739814}

The problem is caused because the `lineEndContext` attribute doesn't work in
empty lines. Now `lineEndContext` works in empty lines, but only if
`lineEmptyContext` is #stay.

Reviewers: #framework_syntax_highlighting, cullmann, dhaumann, vkrause

Reviewed By: #framework_syntax_highlighting, cullmann

Subscribers: kwrite-devel, kde-frameworks-devel

Tags: #kate, #frameworks

Differential Revision: https://phabricator.kde.org/D20148

M  +12   -0    autotests/folding/test.c.fold
M  +12   -0    autotests/html/test.c.html
M  +12   -0    autotests/input/test.c
M  +12   -0    autotests/reference/test.c.ref
M  +17   -2    src/lib/abstracthighlighter.cpp

https://commits.kde.org/syntax-highlighting/b518dcc6486a4dc23785c2d53ae339a9d327e546

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to