- User Since
- Jun 4 2017, 12:22 AM (115 w, 3 d)
The other files that use the include statement are also in version 5.53.
Mon, Aug 19
Sun, Aug 18
Fri, Aug 16
Thu, Aug 15
If it is better not to have a hard-coded color, wouldn't it be better to remove them once and for all? Without necessarily incrementing the version.
I don't think using the original word delimiters is a good thing. Let's imagine that c.xml lists the functions of the libc and a language that allows them to be used as ffi.C.printf (luajit for the curious). The separators of the 2 languages are not the same and puts'plop' works for one, but not for the other. If we rely on the C delimiters, it will not work anymore. I think we can find other examples and perhaps counter-examples.
Wed, Aug 14
- add unit test
- increase version
Tue, Aug 13
I don't understand why there's so much difference in what's displayed :/
Sat, Aug 10
- don't modify the *.xml files to maintain the compatibility in older versions of KF5
- langauge.xsd: accept only 1 or true for fallthrough attribute
I will hand over the original xml files, that seems preferable to me too.
Fri, Aug 9
The 410477 did not exist when I started my modifications, I add it in the list.
Thu, Aug 8
At first, I didn't have much change. But as I broke my teeth on one of the bugs and there were some problems here and there, I armed myself with a bulldozer :D
increase the version number
Wed, Aug 7
Jun 30 2019
After reflection (:D), I think the constraint is weak, the creation of new syntax is rare compared to the rest.
Jun 8 2019
Jun 6 2019
I am confused, the generation of index.katesyntax fails because the list "variables" does not exist (there is no variable predefined in this context). We may be in a situation where a change of branch does not recompile the index file :/.
Jun 4 2019
oops, missing version increase
- fix module
- remove hard coded color
Jun 1 2019
I left it because it goes well with dark or light themes, but I removed it. Is the policy the same for bold, underlined and italic as for color? Because a basic applied distinction between Comment and CommentTitle seems to me preferable. I imagine not, but I would like to be sure.
May 30 2019
OK I understand. Initially I had not changed the version number of txsh.xml and it is based on the reference in /usr/share/org.kde.syntax-highlighting/syntax/index.katesyntax rather than in the repository.
And the fact that the versions in the index file were newer than my xml files... I had errors with highlight.fish.
May 27 2019
I forgot to ask about running the tests. Is it normal that system syntax files take precedence if we have an index.katesyntax? Currently I have to run the tests by setting the environment variable XDG_DATA_DIRS.
May 26 2019
Jan 10 2019
I agree that some rules are excessive or even false, but the last time I watched (it was several months ago now), some regexes suggested to be DetectString seemed to have writing errors (mainly \\ count as 2 characters in xml) and some more or less useful propositions. If there has been no change at this level, it should still be checked.
Sep 30 2018
- fix the recursion detection and handling of nested included keyword lists
Sep 17 2018
(I inadvertently edit the operators list in the previous commit)
- restore operators list
- lazy load keyword lists
Sep 16 2018
resolveIncludeKeywords() would then use loadKeywords() instead of load() ? This should be enough.
Sep 15 2018
Sorry to answer so late, I had trouble logging in.
Sep 9 2018
include rule in keyword list to import those from another file
Aug 19 2018
Yes, my compilation folder was pointing to my fork on github from which I make the patches (as I do not have the right version for ECM, I have a script that does among other things a new CMakeLists.txt in another folder and adds symbolic links for project files). If there was no more error it was because I saw them in the conflicts.
Aug 13 2018
Ok, i'm doing this in the week.
There have been changes in the xml files that will cause conflicts. I would look in the next few days.
Aug 6 2018
I just thought of Definition::keywordLists() which does not list the keywords used by this new syntax.
Aug 5 2018
Aug 4 2018
Yes, I can start tomorrow.
I copied all the keywords in the css.xml file and it's a shame. I think that Keyword could refer to those of other files with ## as for IncludeRules.
Aug 1 2018
Jul 27 2018
Jul 23 2018
Jul 22 2018
Jul 16 2018
It is done. So much emotion :')
Jul 15 2018
Jul 14 2018
Thank you, but I already made the request and it was accepted last night. I will do the next push :)
Jul 1 2018
Jun 23 2018
I do not have a developer account, but I can do it. This is not a problem because I will contribute again.
Jun 18 2018
Jun 16 2018
- C++: test with clang:: in an attribute
Jun 7 2018
May 21 2018
@dhaumann The difference is in the dynamic attribute of a context. Kate propagates the captures only if the value is true whereas SyntaxHighlighting never looks at that value and only uses the dynamic attribute of the rules.
May 14 2018
- Awk: add collating symbols and equivalence classes