Bug 431036 - The syntax highlighting for BASH files didn't handle backticks properly
Summary: The syntax highlighting for BASH files didn't handle backticks properly
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: syntax (other bugs)
Version First Reported In: 20.12.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-01 16:26 UTC by Joerg Schiermeier
Modified: 2021-01-18 21:14 UTC (History)
1 user (show)

See Also:
Latest Commit: https://invent.kde.org/frameworks/syntax-highlighting/commit/f6607c869cf0f5113d657f713fc35fd66a13b8f1
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Screenshot: syntax highlighting before and after the backticks (124.07 KB, image/png)
2021-01-01 16:26 UTC, Joerg Schiermeier 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Joerg Schiermeier 2021-01-01 16:26:36 UTC 
Created attachment 134439 [details]
Screenshot: syntax highlighting before and after the backticks

BASH: Syntax highlighting didn't handle backticks properly


STEPS TO REPRODUCE
In a BASH script which I wrote long time ago I have this line:

if  [ 0 -eq `id -u` ];

When I open this script with Kate the syntax highlighting for the rest of the BASH file isn't realy conclusive. In other words: it is totally broken. This was working properly before Kate twenty something appears. Now is not so nice - or let me say: rubbish.

Backticks are old and busted in the BASH language but they are still working and in a lot of our servers scripts present.


SOFTWARE/OS VERSIONS
Windows: -
macOS: -
Linux/KDE Plasma: 5.77.0
(available in About System)
KDE Plasma Version: 5.77.0
KDE Frameworks Version: 5.77.0
Qt Version: 5.15.2


This bug is a regression and similar to #430668.