https://bugs.kde.org/show_bug.cgi?id=512587
Bug ID: 512587
Summary: Syntax highlighting breaks with listings-package if
language defined while starting the environment
Classification: Applications
Product: kile
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: editor
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
Created attachment 187153
--> https://bugs.kde.org/attachment.cgi?id=187153&action=edit
A simple test case
SUMMARY
Syntax highlighting breaks when using the listings -package, if a language is
defined when starting the environment. I.e.
`\begin{lstlisting}[language=python]` will cause all syntax highlighting to be
gray afterwards for the whole remainder of the document, despite the document
being syntactically valid.
As a workaround, one could use \lstset{language=python} instead.
STEPS TO REPRODUCE
1. Load the example document in KILE.
2. Look at syntax highlighting
OBSERVED RESULT
Syntax highlighting will fail / be disabled from the start of the
\begin{lstlisting} until the end of the document (text is grey).
EXPECTED RESULT
Syntax highlighting should work.
SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.0
Kernel Version: 6.16.5-zen1-1-zen (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 PRO 5850U with Radeon Graphics
Memory: 16 GiB of RAM (11.5 GiB usable)
Graphics Processor: AMD Radeon Graphics
kile-git (3.0b4_r3843.g28ec5acd-1)
ADDITIONAL INFORMATION
- The actual language set seems irrelevant and will fail, as long as a valid
language is set (an invalid language will, of course, cause compilation to
fail, but syntax highlighting will still work in Kile).
- (Any?) other key=value pairs is set in a similar way will not cause syntax
highlighting to fail
--
You are receiving this mail because:
You are watching all bug changes.
