- User Since
- Aug 22 2017, 7:25 AM (116 w, 2 d)
Tue, Nov 5
Mon, Nov 4
Sat, Nov 2
Fri, Nov 1
- Increase the menu size according to the font size, to improve the display
Wed, Oct 30
- Increase margin of list - search bar in Windows
Tue, Oct 29
- Restore scroll bar margins
- Fix font size/style
Mon, Oct 28
No, the dynamic flag is used to insert the captures already stored in %N (the captures are stored in the RegExpr rules and then "inserted" in the rules with the dynamic flag)
QFontMetrics::boundingRect(text).width() doesn't deliver an exact value of the text width, since I detected that in some translations and some desktop themes the text goes below the scroll bar. This problem doesn't exist with QFontMetrics::horizontalAdvance(text).
I had also thought about using QRegularExpression::DontCaptureOption, which is equivalent to using (?:...), but I wasn't sure how much the real improvement in performance is. However, disabling captures avoids allocating unnecessary QString for each capture.
Sun, Oct 27
Oct 10 2019
- TypeScript React: fix end-line regex
typescript-react: increase version.
ups! i will correct it
Oct 4 2019
As the delimiters in WordDetect rules were changed in D24378, I updated this diff only by making minor fixes in the Mustache/Handlebars definition.
- Restore WordDetect rules
- Use kateversion="5.44" (WordDetect with insensitive).
Oct 3 2019
- Add comment
i did it in: D24378
I think it makes sense to change this in WorDetect: verify delimiter characters on the left and right edge of the string, either inside or outside the string. I will make another diff with this.
Oct 2 2019
Indeed, WordDetect checks only the boundaries. What happens is that when using WordDetect with <tag, you need a border character before <, when it shouldn't.
That is, <tag will not match in the text: "word<tag>".
It's correct to use RegExpr with <tag\b instead of WordDetect.
Sep 29 2019
- Fix allocation in search names
Sep 26 2019
m_searchName is a pointer to an attribute of a KateFileType object (which may be the string translatedName or name), but in some cases a new string is created.
- Add boolean m_bHasNewSearchName to verify removal of m_searchName.
- Correct format in some comments.
- Remove friend KateModeMenuList and replace it with the "Factory" class.
- Undo changes in Mustache
Sep 25 2019
Sorry, that could go in another diff.
In the definition of Mustashe, I realized that using WordDetect requires a delimiter before <name. For example, writing text<table> doesn't match the WordDetect rule, so I changed it to RegExpr.
Sep 23 2019
In the function KateModeMenuList::updateSelectedItem() an empty QIcon is also created when selecting an item. It would be better to put emptyIcon as an attribute of the class and use it every time.
Sep 14 2019
Sep 3 2019
Sep 2 2019
Aug 30 2019
- Update function names
- Update function names
I also like hasXXOverride().
Aug 27 2019
Aug 25 2019
Yes, it has to do with that bug.
Later I will add the functions to the KSyntaxHighlighting API to correct this.
Aug 24 2019
- Fix bug in blockquotes and improve integration with R Markdown
Aug 23 2019
Aug 20 2019
Aug 19 2019
Aug 9 2019
I think it's an improvement, but the ideal would be to maintain support for fallthrough="bool". That is, if the fallthroughContext attribute is present, assume fallthrough="true", unless "fallthrough=" is explicitly written.
Aug 8 2019
There are many improvements to the Latex highlighter!
Recently I marked bugs 274440, 322081 and others as duplicates (in fact, this patch fixes them well)