[frameworks-syntax-highlighting] [Bug 434485] Matching bracket highlight not visible with Breeze Dark color theme
https://bugs.kde.org/show_bug.cgi?id=434485 --- Comment #4 from Nibaldo G. --- Fixed in KDE Frameworks 5.81, available in Sat April 10, 2021. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 435086] LaTeX: 'cases' inside math environment syntaxing bug
https://bugs.kde.org/show_bug.cgi?id=435086 --- Comment #3 from Nibaldo G. --- Fixed in KDE Frameworks 5.81, available in Sat April 10, 2021. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 435086] LaTeX: 'cases' inside math environment syntaxing bug
https://bugs.kde.org/show_bug.cgi?id=435086 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.81.0 Latest Commit||https://invent.kde.org/fram ||eworks/syntax-highlighting/ ||-/commit/822fe7e46d02b911d9 ||ebfa79038a4f5de93d9dcf CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 434485] Matching bracket highlight not visible with Breeze Dark color theme
https://bugs.kde.org/show_bug.cgi?id=434485 Nibaldo G. changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/syntax-highlighting/ ||-/commit/fb439c46a8e2827841 ||0a06868747ebb0fcf8536d Version Fixed In||5.81.0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431693] Foldable sections in markdown files
https://bugs.kde.org/show_bug.cgi?id=431693 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #2 from Nibaldo G. --- For headers this is very easy to implement, in fact, in the AsciiDoc highlighter the section titles are folded. However, for the following header formats there are problems: Title H1 Subtitle H2 --- Mainly, there are problems determining whether "" corresponds to a horizontal line or a section title. Also the fold should start with "" or "", so the title text will be left out of the fold. Adding folding to lists is also difficult. To highlight the content of the lists we capture the indentation using dynamic rules, but it isn't possible to determine the level of the lists :( -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 434485] Matching bracket highlight not visible with Breeze Dark color theme
https://bugs.kde.org/show_bug.cgi?id=434485 Nibaldo G. changed: What|Removed |Added Product|kate|frameworks-syntax-highlight ||ing Component|syntax |theme CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 432785] javascript-react.xml has external file ref in a Rule's context
https://bugs.kde.org/show_bug.cgi?id=432785 Nibaldo G. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #3 from Nibaldo G. --- I added this context switch to the documentation: """ An identifier, which is a context name, followed by two hashes (##) and another identifier, which is the name of a language definition. This naming is similar to that used in IncludeRules rules and allows you to switch to a context belonging to another syntax highlighting definition, e.g. "SomeContext##JavaScript". Note that it is not possible to use this context switch in combination with #pop, for example, "#pop!SomeContext##JavaScript" is not valid. """ See the commit here: https://invent.kde.org/utilities/kate/-/commit/858b18d7a8d49348e4d4e24531f36e4f93cc6834 The documentation is not updated automatically, so we will have to wait. In case you still have doubts, you can check the KSyntaxHighlighting source code: https://invent.kde.org/frameworks/syntax-highlighting/-/blob/master/src/lib/contextswitch.cpp#L47 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 432785] javascript-react.xml has external file ref in a Rule's context
https://bugs.kde.org/show_bug.cgi?id=432785 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #2 from Nibaldo G. --- This is valid and it works! Using "NoRegExp##JavaScript" switches to the "NoRegExp" context of the "JavaScript" definition. Apparently this type of context switch isn't in the documentation, I will have to add it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 428331] Syntax highlighting PHP/PHP missing
https://bugs.kde.org/show_bug.cgi?id=428331 --- Comment #4 from Nibaldo G. --- In the "PHP/PHP" highlighter, the main context is: The script that generates "PHP (HTML)" inserts these rules in all contexts of the "HTML" highlighter. Basically, in both "PHP/PHP" and "PHP (HTML)", to write PHP code you have to start with , the first one also highlights the HTML code. I guess the following: You may be using a custom "PHP/PHP" highlighter and after updating KDE Frameworks you are using the major version, which is the built-in one. Check the directories "$HOME/.local/share/org.kde.syntax-highlighting/syntax" and "/usr/share/org.kde.syntax-highlighting/syntax" if there are any XML file for PHP. Also check the old directories: "$HOME/.local/share/katepart5/syntax" and "/usr/share/katepart5/syntax". I make this assumption since KDE Frameworks 5.75 was released on Oct 10, 2020 and prior to that date only minor updates have been made to the "PHP/PHP" highlighter: https://invent.kde.org/frameworks/syntax-highlighting/-/commits/master/data/syntax/php.xml Also, I remember 2 years ago there was a bug that showed hidden highlighters in the syntax highlighting selection menu. https://invent.kde.org/frameworks/ktexteditor/-/commit/bb5f34d7224d0b4d891cdf5d804e2fe515d8dc79 You could also attach example files where you experience the problem along with snapshots, so it could be more clear about the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 428331] Syntax highlighting PHP/PHP missing
https://bugs.kde.org/show_bug.cgi?id=428331 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #2 from Nibaldo G. --- The "PHP/PHP" highlighter is hidden, since it is used to generate "PHP (HTML)". Using "PHP (HTML)" is equivalent to "PHP/PHP" only it includes the HTML tags. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 431268] Kate doesn't highlight bold or italic words
https://bugs.kde.org/show_bug.cgi?id=431268 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #1 from Nibaldo G. --- Could you give more details about the problem? Markdown syntax highlighting does highlight bold and italics (for example, **bold**, __bold__, *italic*). Perhaps the problem is because the font you are using in Kate doesn't have bold and italic variants. * Check if bold and italics are highlighted in other syntax highlighters. For example, in C++ or JavaScript keywords like "if", "while" are highlighted in bold. * Indicate the version of KDE Frameworks you are using (In Kate, go to: Help -> About Kate -> Libraries) * Indicates the type of font used (go to: Settings -> Configure Kate... -> Apperance -> Fonts). Here is an example file of the Markdown highlighting: https://kate-editor.org/syntax/data/html/test.markdown.html -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 423680] Very high CPU load when entering a number in C++ syntax
https://bugs.kde.org/show_bug.cgi?id=423680 Nibaldo G. changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.73.0 Status|ASSIGNED|RESOLVED --- Comment #4 from Nibaldo G. --- Fixed in: https://invent.kde.org/frameworks/syntax-highlighting/-/merge_requests/10 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 423680] Very high CPU load when entering a number in C++ syntax
https://bugs.kde.org/show_bug.cgi?id=423680 Nibaldo G. changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 423680] Very high CPU load when entering a number in C++ syntax
https://bugs.kde.org/show_bug.cgi?id=423680 Nibaldo G. changed: What|Removed |Added CC||walter.von.entferndt@posteo ||.net Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax Version|20.04.2 |5.71.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423680] Very high CPU load when entering a number in C++ syntax
https://bugs.kde.org/show_bug.cgi?id=423680 --- Comment #2 from Nibaldo G. --- I did tests on "isocpp.xml": in the "Number" context there is a RegExpr rule with a very large regular expression to detect float numbers. This is responsible for slowing down aand using high CPU by writing numbers in C++/ISO C++ -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 423680] Very high CPU load when entering a number in C++ syntax
https://bugs.kde.org/show_bug.cgi?id=423680 Nibaldo G. changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||nibg...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Nibaldo G. --- In the ISO C++ highlighter (isocpp.xml), to detect a number, many context switches occur (there are 4-5 context switches) and there are many RegExpr rules; since suffixes, number types and invalid characters are highlighted. This may explain the high CPU usage. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 422521] syntax/folding (C/C++): "#..." interferes with std block "{" folding
https://bugs.kde.org/show_bug.cgi?id=422521
Nibaldo G. changed:
What|Removed |Added
CC||nibg...@gmail.com
--- Comment #2 from Nibaldo G. ---
This is very difficult to fully correct. One solution may be to disable the
folding of "{" and "}" inside the block "#else" - "#endif".
For example:
#ifdef SOMETHING
if (a >= b || b >= c) { // <-- Here folding in "{" is activated
#else
if (a < b && b < c) { // <-- Here folding is disabled
#endif
/* code */
}
--
You are receiving this mail because:
You are watching all bug changes.
[kile] [Bug 419125] Code folding seems broken
https://bugs.kde.org/show_bug.cgi?id=419125 --- Comment #5 from Nibaldo G. --- Fixed in KDE Frameworks 5.71.0, available on Sat June 13, 2020. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418876] syntax highlighting for comment in a grep pipe is wrong
https://bugs.kde.org/show_bug.cgi?id=418876 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.71.0 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419125] Code folding seems broken
https://bugs.kde.org/show_bug.cgi?id=419125 Nibaldo G. changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||nibg...@gmail.com --- Comment #3 from Nibaldo G. --- Proposed patch: https://phabricator.kde.org/D29521 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 --- Comment #5 from Nibaldo G. --- Sorry, I was wrong, this bug was fixed in ** KDE Frameworks 5.69.0 ** (not in 5.59) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Version Fixed In|5.59.0 |5.69.0 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 --- Comment #2 from Nibaldo G. --- The bug is the same as #418979, which was fixed in KDE Frameworks 5.59.0. In which version of KDE Frameworks does this bug appear? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added CC||deada...@gmail.com --- Comment #2 from Nibaldo G. --- *** Bug 419484 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 419484] wrong syntax highlighting (editor assumes math environment but it is not)
https://bugs.kde.org/show_bug.cgi?id=419484 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 418979 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 418979] Wrong LaTeX syntax highlighting after braces in optional argument of \cite
https://bugs.kde.org/show_bug.cgi?id=418979 Nibaldo G. changed: What|Removed |Added Version|19.04.3 |5.68.0 Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413626] Bash string highlighting problems
https://bugs.kde.org/show_bug.cgi?id=413626
Nibaldo G. changed:
What|Removed |Added
CC||nibg...@gmail.com
--- Comment #4 from Nibaldo G. ---
I have tried to fix this, but I need more knowledge in Bash, since there is no
simple solution, we must change the way it stands out in content within the
braces ${...}.
I have also seen that this bug is present in more text editors such as Atom,
Visual Studio Code and Sublime Text.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.68.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 416685] Makefile invalid highlight
https://bugs.kde.org/show_bug.cgi?id=416685 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing Version Fixed In||5.68.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 417379] ifeq sequence highlighted invalid
https://bugs.kde.org/show_bug.cgi?id=417379 Nibaldo G. changed: What|Removed |Added Version|unspecified |5.67.0 Product|kate|frameworks-syntax-highlight ||ing CC||nibg...@gmail.com Component|syntax |syntax -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 --- Comment #8 from Nibaldo G. --- https://phabricator.kde.org/D27313 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 --- Comment #7 from Nibaldo G. --- I can add a test file -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 143399] highlighter text style: can't turn off inherited attributes
https://bugs.kde.org/show_bug.cgi?id=143399 Nibaldo G. changed: What|Removed |Added Version Fixed In|5.50.0 |5.62.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 143399] highlighter text style: can't turn off inherited attributes
https://bugs.kde.org/show_bug.cgi?id=143399 --- Comment #8 from Nibaldo G. --- Fixed in: https://phabricator.kde.org/D23515 https://phabricator.kde.org/D23516 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 143399] highlighter text style: can't turn off inherited attributes
https://bugs.kde.org/show_bug.cgi?id=143399 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.50.0 Latest Commit||https://commits.kde.org/kte ||xteditor/00721e80b5b42c7f1f ||cf0b530eee9dde1cc173ef -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 143399] highlighter text style: can't turn off inherited attributes
https://bugs.kde.org/show_bug.cgi?id=143399 Nibaldo G. changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #7 from Nibaldo G. --- Yes, it's fixed! -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415384] LaTeX braces matching in \input is off
https://bugs.kde.org/show_bug.cgi?id=415384 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #3 from Nibaldo G. --- Fixed in KDE Frameworks 5.66 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415384] LaTeX braces matching in \input is off
https://bugs.kde.org/show_bug.cgi?id=415384 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.66.0 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 415384] LaTeX braces matching in \input is off
https://bugs.kde.org/show_bug.cgi?id=415384
Nibaldo G. changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED|RESOLVED
Latest Commit||https://commits.kde.org/syn
||tax-highlighting/6ddf50d243
||dd973614dc5f57f366cb952310a
||2cd
--- Comment #1 from Nibaldo G. ---
Git commit 6ddf50d243dd973614dc5f57f366cb952310a2cd by Nibaldo González.
Committed on 23/12/2019 at 01:03.
Pushed by ngonzalez into branch 'master'.
LaTeX: fix brackets in some commands
Summary:
In the parameter of some commands, such as `\input{\a{}}`, the brackets are
closed incorrectly, which causes the pairs of brackets to be marked
incorrectly.
Reviewers: #framework_syntax_highlighting, cullmann
Reviewed By: #framework_syntax_highlighting, cullmann
Subscribers: cullmann, kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D26151
M +4-0autotests/folding/highlight.tex.fold
M +4-0autotests/html/highlight.tex.html
M +4-0autotests/input/highlight.tex
M +4-0autotests/reference/highlight.tex.ref
M +3-1data/syntax/latex.xml
https://commits.kde.org/syntax-highlighting/6ddf50d243dd973614dc5f57f366cb952310a2cd
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 414996] Python HL does not highlight octal numbers
https://bugs.kde.org/show_bug.cgi?id=414996 Nibaldo G. changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.66.0 Latest Commit||https://commits.kde.org/syn ||tax-highlighting/8ca7064781 ||a328b33b2cd79668e876719f1cc ||762 --- Comment #2 from Nibaldo G. --- Git commit 8ca7064781a328b33b2cd79668e876719f1cc762 by Nibaldo González. Committed on 13/12/2019 at 02:22. Pushed by ngonzalez into branch 'master'. Python: improve numbers, add octals, binaries and "breakpoint" keyword Summary: FIXED-IN: 5.66.0 **Changes:** * Improve number detection with underscores. Add binaries and octales. (I took the regular expressions from the TypeScript highlighting file and adapted them to Python). See: https://www.python.org/dev/peps/pep-0515/ * Add keyword "breakpoint" introduced in Python 3.7: https://www.python.org/dev/peps/pep-0553/ Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, dhaumann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D25869 M +32 -0autotests/folding/test.py.fold M +36 -4autotests/html/test.py.html M +32 -0autotests/input/test.py M +36 -4autotests/reference/test.py.ref M +21 -16 data/syntax/python.xml https://commits.kde.org/syntax-highlighting/8ca7064781a328b33b2cd79668e876719f1cc762 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 414996] Python HL does not highlight octal numbers
https://bugs.kde.org/show_bug.cgi?id=414996 Nibaldo G. changed: What|Removed |Added Version|unspecified |5.64.0 Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 414996] Python HL does not highlight octal numbers
https://bugs.kde.org/show_bug.cgi?id=414996 Nibaldo G. changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||nibg...@gmail.com --- Comment #1 from Nibaldo G. --- The HlCOct rule is equivalent to "\b0[0-7]+". I corrected the numbers in: https://phabricator.kde.org/D25869 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413493] LaTeX highlighter ignores \end{equation} in corner cases.
https://bugs.kde.org/show_bug.cgi?id=413493
Nibaldo G. changed:
What|Removed |Added
Latest Commit||https://commits.kde.org/syn
||tax-highlighting/467bea3525
||cc5fde844ef6ca4d56fd68c7df9
||e05
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
Version Fixed In||5.64.0
--- Comment #3 from Nibaldo G. ---
Git commit 467bea3525cc5fde844ef6ca4d56fd68c7df9e05 by Nibaldo González.
Committed on 05/11/2019 at 02:09.
Pushed by ngonzalez into branch 'master'.
LaTeX: fix backslash delimiter in some keywords
Summary:
FIXED-IN: 5.64.0
A delimiter before keywords of kind `\command` isn't required. Therefore, a
DetectChar rule with lookAhead is used to detect `\` at the beginning of the
keywords, and thus avoid the delimiter in the keyword.
{F7733046}
Reviewers: #framework_syntax_highlighting, dhaumann, cullmann, jpoelen
Reviewed By: #framework_syntax_highlighting, cullmann
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D25139
M +9-0autotests/folding/highlight.tex.fold
M +9-0autotests/html/highlight.tex.html
M +9-0autotests/input/highlight.tex
M +9-0autotests/reference/highlight.tex.ref
M +38 -16 data/syntax/latex.xml
https://commits.kde.org/syntax-highlighting/467bea3525cc5fde844ef6ca4d56fd68c7df9e05
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413409] No VHDL highlight for uppercase VHDL keywords
https://bugs.kde.org/show_bug.cgi?id=413409 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.64.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413409] No VHDL highlight for uppercase VHDL keywords
https://bugs.kde.org/show_bug.cgi?id=413409 Nibaldo G. changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/5f0306281a ||954af832e12d4083175bbd93ca4 ||e4d --- Comment #2 from Nibaldo G. --- Git commit 5f0306281a954af832e12d4083175bbd93ca4e4d by Nibaldo González. Committed on 02/11/2019 at 01:39. Pushed by ngonzalez into branch 'master'. VHDL: all keywords are insensitive Summary: In the VHDL highlighter all the rules have the **insensitive** flag, except two, probably by mistake. I also add `##Alerts` in comments. Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D25102 M +7-0autotests/folding/light52_tb.vhdl.fold M +1-1autotests/html/light52_muldiv.vhdl.html M +8-1autotests/html/light52_tb.vhdl.html M +7-0autotests/input/light52_tb.vhdl M +1-1autotests/reference/light52_muldiv.vhdl.ref M +8-1autotests/reference/light52_tb.vhdl.ref M +6-4data/syntax/vhdl.xml https://commits.kde.org/syntax-highlighting/5f0306281a954af832e12d4083175bbd93ca4e4d -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413626] Bash string highlighting problems
https://bugs.kde.org/show_bug.cgi?id=413626 Nibaldo G. changed: What|Removed |Added Version|19.08.2 |5.63.0 Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 413409] No VHDL highlight for uppercase VHDL keywords
https://bugs.kde.org/show_bug.cgi?id=413409 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #1 from Nibaldo G. --- I checked the VHDL highlighter and found a couple of rules without the insensitive flag: https://phabricator.kde.org/D25102 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 --- Comment #2 from Nibaldo G. --- Also, the keywords "reserved" are highlighted with "Error", I don't know if it's intentional, but I think it's good -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #1 from Nibaldo G. --- I don't know this language, however I have tested with the GitHub sample files (https://github.com/ethereum/solidity/) and it looks good. If you want, you can send it to the repository to include it. In that case, it's necessary that you also add a test file in "autotests/input/". This is the KSyntaxHighlighting repository: https://phabricator.kde.org/source/syntax-highlighting/ The XML files are located in "data/syntax/". Here is the documentation for publishing patches: https://community.kde.org/Infrastructure/Phabricator If you think the highlighting file can be improved, you can publish patches in the future, modifying it without problems. In case you don't have time to do all that, you can upload the test file here and I will publish the highlighter file. Some recommendations: * On line 284, add `` to also highlight comments with documentation. * If possible, use the MIT license in the .xml file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411867] [New Syntax] Highlighting for Solidity (Ethereum)
https://bugs.kde.org/show_bug.cgi?id=411867 Nibaldo G. changed: What|Removed |Added Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411508] Digraphs and trigraphs in C and C++ are not handled correctly
https://bugs.kde.org/show_bug.cgi?id=411508 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.62.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411508] Digraphs and trigraphs in C and C++ are not handled correctly
https://bugs.kde.org/show_bug.cgi?id=411508 --- Comment #2 from Nibaldo G. --- Proposed patch: https://phabricator.kde.org/D23691 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411508] Digraphs and trigraphs in C and C++ are not handled correctly
https://bugs.kde.org/show_bug.cgi?id=411508
Nibaldo G. changed:
What|Removed |Added
CC||nibg...@gmail.com
--- Comment #1 from Nibaldo G. ---
Digraphs can be easily added.
The trigraphs were removed in C++17 and are almost in disuse in C, do you think
it is necessary to add them also to the C highlighter? For example, at least,
the folding of ??< and ??> (equivalent to { and }).
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 411508] Digraphs and trigraphs in C and C++ are not handled correctly
https://bugs.kde.org/show_bug.cgi?id=411508 Nibaldo G. changed: What|Removed |Added Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax Version|19.08.0 |5.61.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410472] [New Syntax] MiniZinc syntax highlight
https://bugs.kde.org/show_bug.cgi?id=410472 Nibaldo G. changed: What|Removed |Added Summary|MiniZinc syntax highlight |[New Syntax] MiniZinc ||syntax highlight -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 392972] [New Syntax] AutoIt highlighting support
https://bugs.kde.org/show_bug.cgi?id=392972 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Status|RESOLVED|REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 392972] [New Syntax] AutoIt highlighting support
https://bugs.kde.org/show_bug.cgi?id=392972 Nibaldo G. changed: What|Removed |Added Summary|AutoIt highlighting support |[New Syntax] AutoIt ||highlighting support -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 370459] [New Syntax] Could you add ats mode for kate?
https://bugs.kde.org/show_bug.cgi?id=370459 Nibaldo G. changed: What|Removed |Added Summary|Could you add ats mode for |[New Syntax] Could you add |kate? |ats mode for kate? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 392468] [New Syntax] No Perl 6 syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=392468 Nibaldo G. changed: What|Removed |Added Summary|No Perl 6 syntax|[New Syntax] No Perl 6 |highlighting|syntax highlighting -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 381547] [New Syntax] Add Syntax Support for Renpy .rpy files
https://bugs.kde.org/show_bug.cgi?id=381547 Nibaldo G. changed: What|Removed |Added Summary|Add Syntax Support for |[New Syntax] Add Syntax |Renpy .rpy files|Support for Renpy .rpy ||files -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 390309] Markdown: Bold style not applied when underscore(s) presented in text surrounded by ** or __
https://bugs.kde.org/show_bug.cgi?id=390309 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.62.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 390309] Markdown: Bold style not applied when underscore(s) presented in text surrounded by ** or __
https://bugs.kde.org/show_bug.cgi?id=390309
Nibaldo G. changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED|RESOLVED
Latest Commit||https://commits.kde.org/syn
||tax-highlighting/c461c5a78f
||c8f952a31d7ea846ebd2eeb2278
||cd6
--- Comment #1 from Nibaldo G. ---
Git commit c461c5a78fc8f952a31d7ea846ebd2eeb2278cd6 by Nibaldo González.
Committed on 24/08/2019 at 09:45.
Pushed by ngonzalez into branch 'master'.
Markdown: multiple improvements and fixes
Summary:
## Improve & fix detection of bold/italic text
In bold and italic text highlighting, underscores and asterics aren't allowed
inside, for example `**some_text**` isn't highlighted correctly. I have
improved regex to detect bold and italic text: now asterisks, underscores and
escapes are allowed inside.
{F7273185}
## Improve fenced code blocks
The way to write fenced code blocks varies depending on the
Markdown/MultiMarkdown implementation. Some support only 3 backticks, others
more than 3 backticks, others both; and others 3 tildes (`~`). [1]
Therefore, I think it's a good idea to support all implementations: code blocks
can be written with 3 backticks or more, or with 3 tildes or more . Other
editors, such as Visutal Studio Code, Atom and Sublime Text highlight fenced
code blocks in this way.
Unfortunately, this is only possible using dynamic rules with several RegExpr,
which isn't very optimal. I have no problem modifying that if you don't like
it.
{F7273187}
**Also:**
* Add folding in fenced code blocks.
* Add more keywords to identify languages.
* Add to highlight in fenced code blocks the languages that are already loaded
by default, since they are included via IncludeRules (JavaScript, TypeScript,
JSX, SQL, Mustache/Handlebars, reST & Doxygen).
* Add more languages in the code blocks. Some of the most popular languages are
included [3] [4]: C, Go, Java, JavaScript, TypeScript, Matlab, Perl, R & Ruby.
## Improve code blocks
* Highlight single code with more than one backticks. [2]
{F7273189}
* Fix: highlight indented code only after an empty line.
{F7273193}
## Improve highlighting of links and references
{F7273195}
## Improve metadata highlighting
Previously, some metadata Keys were highlighted anywhere in the document. Now
the metadata is highlighted only on the first line of the Markdown document.
[6] [7]
{F7273196}
## Improves list detection
Through dynamic rules, the indentation of lists is captured, in order to
correctly highlight the indented content in them.
Now the text within the lists is highlighted using "dsNormal", so as not to
saturate Markdown documents with many colors.
{F7273197}
## Add support of inline HTML
`IncludeRules` is used to highlight only HTML tags. [8]
## Others
* Highlight checkboxs in lists.
{F7273202}
* Add escape characters [5].
* Add `##Alerts` and `##Modelines` in the comments.
* Some minor improvements, such as replacing some RegExpr rules and adding
`column="0"` in some rules.
**Sources:**
* [1] Fenced Markdown code blocks:
<https://meta.stackexchange.com/questions/125148/implement-style-fenced-markdown-code-blocks/143705#143705>
* [2] Markdown Syntax Documentation. Code:
<https://daringfireball.net/projects/markdown/syntax#code>
* [3] GitHut - Programming Languages and GitHub: <https://githut.info/>
* [4] Most Popular and Influential Programming Languages of 2018:
<https://stackify.com/popular-programming-languages-2018/>
* [5] Markdown Syntax Documentation. Backslash escapes:
<https://daringfireball.net/projects/markdown/syntax#backslash>
* [6] MutiMarkdown Metadata:
<https://fletcher.github.io/MultiMarkdown-5/metadata.html>
* [7] Markdown metadata format:
<https://stackoverflow.com/questions/44215896/markdown-metadata-format>
* [8] Markdown Syntax Documentation. Inline HTML:
<https://daringfireball.net/projects/markdown/syntax#html>
Reviewers: cullmann, dhaumann, #framework_syntax_highlighting
Reviewed By: dhaumann, #framework_syntax_highlighting
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D23371
M +40 -11 autotests/folding/example.rmd.fold
M +453 -53 autotests/folding/test.markdown.fold
M +2-2autotests/html/basic.markdown.html
M +35 -6autotests/html/example.rmd.html
M +414 -14 autotests/html/test.markdown.html
M +29 -0autotests/input/example.rmd
M +405 -5autotests/input/test.markdown
M +3-3autotests/reference/basic.markdown.ref
M +37 -8autotests/reference/example.rmd.ref
M +467 -67 autotests/
[frameworks-syntax-highlighting] [Bug 390309] Markdown: Bold style not applied when underscore(s) presented in text surrounded by ** or __
https://bugs.kde.org/show_bug.cgi?id=390309 Nibaldo G. changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|nibg...@gmail.com CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.62.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added CC||loic.gro...@gmail.com --- Comment #5 from Nibaldo G. --- *** Bug 322144 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 322144] Bad parsing of environments nested in math environment
https://bugs.kde.org/show_bug.cgi?id=322144 Nibaldo G. changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||nibg...@gmail.com --- Comment #8 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 410477 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 322081] Highlighting problem using aligned environment within equation environment
https://bugs.kde.org/show_bug.cgi?id=322081 Nibaldo G. changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||nibg...@gmail.com --- Comment #6 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 410477 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added CC||ali.i.a.o...@gmail.com --- Comment #4 from Nibaldo G. --- *** Bug 322081 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added CC||sh200...@mail.ru --- Comment #3 from Nibaldo G. --- *** Bug 408297 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 408297] \end{gathered} not highligted correctly
https://bugs.kde.org/show_bug.cgi?id=408297 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 410477 *** -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 274440] Kile: syntax highlighting failed to match aligned environment within equation
https://bugs.kde.org/show_bug.cgi?id=274440 Nibaldo G. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||nibg...@gmail.com --- Comment #16 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 410477 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added CC||outermeas...@mail.org --- Comment #2 from Nibaldo G. --- *** Bug 274440 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added Assignee|kwrite-bugs-n...@kde.org|nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477
Nibaldo G. changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #1 from Nibaldo G. ---
When writing "\end{something}" within a Math environment, the highlighter
considers it as the end of the same Math environment. For example, in this
case, the highlighter believes that "\end{split}" is the end of "equation", but
shows incorrect highlighting, since "split" doesn't correspond to a valid
keyword of a Math environment.
I will upload a patch to fix it.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410477] Syntax Highlighting LaTeX: wrong color for \end{split} in environment equation
https://bugs.kde.org/show_bug.cgi?id=410477 Nibaldo G. changed: What|Removed |Added Component|syntax |syntax Version|Git |5.60.0 Product|kate|frameworks-syntax-highlight ||ing CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 410472] MiniZinc syntax highlight
https://bugs.kde.org/show_bug.cgi?id=410472 Nibaldo G. changed: What|Removed |Added Component|syntax |syntax Version|19.04.3 |5.60.0 Product|kate|frameworks-syntax-highlight ||ing CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 403901] No constants highlighting for Julia
https://bugs.kde.org/show_bug.cgi?id=403901 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.60.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 403901] No constants highlighting for Julia
https://bugs.kde.org/show_bug.cgi?id=403901 Nibaldo G. changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/c91c255421 ||5d578dd688d890f12011333189d ||578 --- Comment #6 from Nibaldo G. --- Git commit c91c2554215d578dd688d890f12011333189d578 by Nibaldo González. Committed on 15/06/2019 at 09:13. Pushed by ngonzalez into branch 'master'. Julia: update syntax and add constants keywords Summary: Update Julia's syntax with some missing features, such as multi-line comments and strings, based on Julia's documentation. It also adds keywords of constants and types. **Changes in julia.xml:** * Add missing keywords. Add keywords of constants and modules. * Numbers: * Allow underscores in numbers. * Add hexadecimal floating-point. * Add octales and binaries. * Add multi-line comments. * Add multi-line strings, raw strings, docs strings, byte arrays and Regex strings. * Add command strings (with backstricks). * Replace rules StringDetect with Detect2Chars in the detection of operators. **Source:** * Julia 1.1 Documentation: https://docs.julialang.org/en/v1.1/ Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D21711 A +73 -0autotests/folding/test.jl.fold A +80 -0autotests/html/test.jl.html A +73 -0autotests/input/test.jl A +73 -0autotests/reference/test.jl.ref M +459 -40 data/syntax/julia.xml https://commits.kde.org/syntax-highlighting/c91c2554215d578dd688d890f12011333189d578 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 403901] No constants highlighting for Julia
https://bugs.kde.org/show_bug.cgi?id=403901 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #5 from Nibaldo G. --- I made a patch updating the syntax of Julia, if you could review it would be great: https://phabricator.kde.org/D21711 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block
https://bugs.kde.org/show_bug.cgi?id=407060
Nibaldo G. changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Latest Commit||https://commits.kde.org/syn
||tax-highlighting/28b11e39fb
||a077fc1b41e27ee31439a331fd0
||66e
Resolution|--- |FIXED
Version Fixed In||5.59.0
--- Comment #3 from Nibaldo G. ---
Git commit 28b11e39fba077fc1b41e27ee31439a331fd066e by Nibaldo González.
Committed on 31/05/2019 at 18:58.
Pushed by ngonzalez into branch 'master'.
YAML: only comments after spaces and other improvements/fixes
Summary:
FIXED-IN: 5.59.0
Improvements and corrections to YAML.
**Changes:**
* Only highlight comments after spaces.
* Add folding indentation, like the Python highlighter.
* Avoid highlighting lists, hashes and strings within blocks with multiple
lines, incorrectly.
* Highlight two points of Keys in another color, to make it easier to
differentiate Keys and attributes in some color schemes.
* Changes in colors:
* The Keys are now in bold, helps to differentiate Keys and attributes,
especially in the Solarized schemes.
* Data types are highlighted with `dsOthers`, to differentiate from the
Attribute color.
* "Normal Text" is now `dsAttribute`, to unify the colors of attributes,
since in attributes with multiple lines the colors are inconsistent. This is
done according to other text editors such as VSCode and Atom, where the same
color is used for attributes and normal text.
{F6849805}
{F6849807}
Solarized scheme:
{F6849808}
Normal block & literal block:
{F6849809}
Reviewers: dhaumann, cullmann, #framework_syntax_highlighting
Reviewed By: dhaumann, cullmann, #framework_syntax_highlighting
Subscribers: kwrite-devel, kde-frameworks-devel
Tags: #kate, #frameworks
Differential Revision: https://phabricator.kde.org/D21411
M +34 -28 autotests/folding/test.yaml.fold
M +4-4autotests/html/example.rmd.html
M +98 -92 autotests/html/test.yaml.html
M +6-0autotests/input/test.yaml
M +4-4autotests/reference/example.rmd.ref
M +89 -83 autotests/reference/test.yaml.ref
M +190 -127 data/syntax/yaml.xml
https://commits.kde.org/syntax-highlighting/28b11e39fba077fc1b41e27ee31439a331fd066e
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block
https://bugs.kde.org/show_bug.cgi?id=407060 --- Comment #2 from Nibaldo G. --- Proposed patch: https://phabricator.kde.org/D21411 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block
https://bugs.kde.org/show_bug.cgi?id=407060 Nibaldo G. changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407060] incorrect YAML highlighted some text block
https://bugs.kde.org/show_bug.cgi?id=407060 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Assignee|kwrite-bugs-n...@kde.org|nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407763] Syntax highlighting reverts default "guess" when editing remote files when saving
https://bugs.kde.org/show_bug.cgi?id=407763 Nibaldo G. changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/kte ||xteditor/b2064042daa143ae60 ||d5728d46777511aee74a02 Resolution|--- |FIXED --- Comment #3 from Nibaldo G. --- Git commit b2064042daa143ae60d5728d46777511aee74a02 by Nibaldo González. Committed on 22/05/2019 at 11:25. Pushed by ngonzalez into branch 'master'. Fix: don't reset Highlight when saving some files Summary: Fix the regression of patch D20959. In sftp:// or fish:// files, the current syntax highlighting isn't stored in `$HOME/.config/katemetainfos`. Therefore, when saving a file, the highlighting is reset. This only happens when changing the hl from the "Highlighting" menu, not from the "Mode" menu. Basically, this returns to the state before the patch D20959, but now the highlight will always change if `user` is true. Reviewers: #ktexteditor, cullmann Reviewed By: #ktexteditor, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D21331 M +4-2src/document/katedocument.cpp https://commits.kde.org/ktexteditor/b2064042daa143ae60d5728d46777511aee74a02 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 407763] Syntax highlighting reverts default "guess" when editing remote files when saving
https://bugs.kde.org/show_bug.cgi?id=407763 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com --- Comment #2 from Nibaldo G. --- Proposed fix: https://phabricator.kde.org/D21331 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 Nibaldo G. changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/71446d3e9e ||5eda6b524be81726dd461f7c942 ||f1e Resolution|--- |FIXED --- Comment #6 from Nibaldo G. --- Git commit 71446d3e9e5eda6b524be81726dd461f7c942f1e by Nibaldo González. Committed on 19/05/2019 at 11:48. Pushed by ngonzalez into branch 'master'. Remove .conf extension from "INI Files" hl, to determine the highlighter using MIME type Summary: The extension `.conf` is very generic, since depending on the context, it can be used with a different language, and assigning it to the "INI Files" highlighter isn't very convenient. For example, in "Fontconfig" the XML files have a `.conf` extension. Therefore, I propose that the `.conf` extension isn't assigned to any syntax highlighter, so use the MIME type to determine the highlighting mode in those files. For example, when applying this patch, the Fontconfig files (located in `/etc/fonts/`) are highlighted as XML by default. Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D21288 M +1-1data/syntax/ini.xml https://commits.kde.org/syntax-highlighting/71446d3e9e5eda6b524be81726dd461f7c942f1e -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407327] Perl5 syntax highlight gets confused at //
https://bugs.kde.org/show_bug.cgi?id=407327 Nibaldo G. changed: What|Removed |Added Version Fixed In||5.59.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407327] Perl5 syntax highlight gets confused at //
https://bugs.kde.org/show_bug.cgi?id=407327 Nibaldo G. changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/syn ||tax-highlighting/4cf3a7e982 ||5da99914e3641fb484270813943 ||d08 Status|REPORTED|RESOLVED --- Comment #1 from Nibaldo G. --- Git commit 4cf3a7e9825da99914e3641fb484270813943d08 by Nibaldo González. Committed on 19/05/2019 at 11:41. Pushed by ngonzalez into branch 'master'. Perl: fix the // operator Summary: The "/" character is used for patterns and this causes the "//" operator not to be highlighted correctly in some situations, such as after identifiers. Reviewers: #framework_syntax_highlighting, dhaumann, cullmann Reviewed By: #framework_syntax_highlighting, dhaumann, cullmann Subscribers: kwrite-devel, kde-frameworks-devel Tags: #kate, #frameworks Differential Revision: https://phabricator.kde.org/D21286 M +4-0autotests/folding/highlight.pl.fold M +4-0autotests/html/highlight.pl.html M +4-0autotests/input/highlight.pl M +4-0autotests/reference/highlight.pl.ref M +6-3data/syntax/perl.xml https://commits.kde.org/syntax-highlighting/4cf3a7e9825da99914e3641fb484270813943d08 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 --- Comment #5 from Nibaldo G. --- Proposed patch: https://phabricator.kde.org/D21288 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 --- Comment #4 from Nibaldo G. --- For syntax highlighting, the extensions have priority over the MIME type, and the extension ".conf" is assigned the "INI Files" highlighter. Another simple solution is to remove "*.conf" from the "INI Files" highlighter; then the .conf extension will not have an assigned syntax highlight and the MIME type will be used to define the appropriate highlight. There the XML highlighting will be used by default in the .conf files that have XML content, as in the case of Fontconfig files. That is a good solution, since the extension .conf is very generic to assign it to a specific highlighter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 405824] Markdown syntax: give bullet lists a more readable color
https://bugs.kde.org/show_bug.cgi?id=405824 --- Comment #1 from Nibaldo G. --- The lists are highlighted with the "dsFloat" color style, which is yellow in the "Normal" scheme and orange in the "KDE" scheme, which can be difficult to read when there is a lot of text. I propose to change dsFloat => dsString in lists and dsBaseN => dsVerbatimString in code. since the "dsString" color style is designed for text strings and is readable in all color schemes (this is red in most schemes). what do you think? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 149313] add support for HAML and SASS syntax highlighting
https://bugs.kde.org/show_bug.cgi?id=149313 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 345003] syntax highlighting for jsp incomplete
https://bugs.kde.org/show_bug.cgi?id=345003 Nibaldo G. changed: What|Removed |Added CC||nibg...@gmail.com Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407327] Perl5 syntax highlight gets confused at //
https://bugs.kde.org/show_bug.cgi?id=407327 Nibaldo G. changed: What|Removed |Added Version|18.08.0 |5.57.0 Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 405824] Markdown syntax: give bullet lists a more readable color
https://bugs.kde.org/show_bug.cgi?id=405824 Nibaldo G. changed: What|Removed |Added Version|unspecified |5.57.0 Product|kate|frameworks-syntax-highlight ||ing Component|syntax |syntax CC||nibg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 404221] Contents of C/C++ macros should also be highlighted like other code
https://bugs.kde.org/show_bug.cgi?id=404221 Nibaldo G. changed: What|Removed |Added Component|syntax |syntax Product|kate|frameworks-syntax-highlight ||ing -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400290] Syntax highlighting engine makes wrong guesses for XML files with different extension
https://bugs.kde.org/show_bug.cgi?id=400290 Nibaldo G. changed: What|Removed |Added CC||i...@guoyunhe.me --- Comment #3 from Nibaldo G. --- *** Bug 407297 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 407297] XML files with *.conf are syntax highlighted as INI
https://bugs.kde.org/show_bug.cgi?id=407297 Nibaldo G. changed: What|Removed |Added Resolution|--- |DUPLICATE CC||nibg...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from Nibaldo G. --- *** This bug has been marked as a duplicate of bug 400290 *** -- You are receiving this mail because: You are watching all bug changes.
