Some languages supported by Kitty, such as Scyndi, NIL, Lua and JavaScript accept both " and ' as string starts, and endings, and it won't matter which you use as long as you a consequent. Kitty will for these languages only deem " acceptable now, but of course, that's not really good, now is it?
I need to sort out how I can cover that best....

Programming languages

• C/C++ (will be considered one language as far as Kitty is concerned)
• Pascal
• BlitzMax
• BlitzBASIC / BlitzPlus / Blitz3D
• BASIC/QBASIC
• Scyndi
• Python
• Lua
• NIL
• C#
• Java
• JavaScript
• Go
• SASKIA
• VisualBasic (no promises yet)
• Assembler (no promises yet)

Configuration languages:

• GINI
• INI
• JSON
• MyData (not sure if I deem this a config language, but for now the best place to put this).

Markup languages (this will be very tricky)

• HTML/XML
• MarkDown

EsoLangs:

• BrainFuck
• WhiteSpace

If the language you desire is not listed here, feel free to suggest it. If it's doable for me, I'll add it to this list, if I know too little about the language, you may try to create a class yourself which can be added to Kitty and throw in a pull request, so I can evaluate. (Oh yeah, I guess it's obvious I'll need example code so I can test stuff out).

For now I'll leave it to basic .NET color support, but when used with tools such as LESS, this is not the best approach (although I guess in Unix based systems Mono does this by default?)

Base types are for strongtype languages (such as C, Pascal, etc) the types that are always present from the start... For C/C++ that would be int and char, for go that would be int, string, map, to name a few, and for C# int, char, byte, long, strong... well and so I can rant on....

These base types are currently seen as keywords, but there is always a bit of debate if they should be regarded as such by syntax highlighters.

This merely means that Kitty will be asking you to press a key after a certain set of lines, and I do plan to make it detect how many lines fit on the screen (although as a kind of security measure, it will only make this detection at the start of the viewing, so if you resize the screen while in session you can mess this up).

Due to the expansion to my units this should be doable

@freezernick

You did the highlight for Visual Basic back in the time. It's been too long since I used Visual Basic last, so perhaps I can best leave this one to you. I've put in "Base Type" support.... If you highlight a source written in C or C++ you'll see that words as "int", "char" and "void" which refer to the default types C and C++ offer (without including any libraries) will now light up in magenta (or purple if you like). Keywords that do not refer to types, such as "if" and "while" etc are still yellow, as they used to be. Perhaps you can take a look if you can group the base types of VB together. It works the same as with keywords... BaseTypes.Add("int"); will add "int" to the base types. And since VB is case insenstive, you need to make sure all base types are in lower case.

Make sure to set your fork up-to-date, as I had to do a few core changes in Kitty to make this all possible.

While adding the missing unreserved keywords I realized that both C# and C++ don't have highlighting of #region or #pragma region / #pragma endregion respectively.

We will probably add this to our fork but the question would be if you want to have it too.
I will make the PR ( #11 ) for the unreserved keywords as a draft until you decide.

No idea what causes it, but I'll be looking into it when I got the time.

Languages like Pascal and loads of variants of the BASIC programming language will need this.

Since BlitzMax has a bit of an odd approach to this, there is no support for this, yet!

Did I screw up or did you forget to update your TrickyUnits repository? 😛