#868 txt2tags syntax highlight is broken since geany 1.22
After an update to geany 1.22 on Archlinux, I discovered the syntax highlight is no longer working as expected. It used to look like this before:
http://img208.imageshack.us/img208/2494/scitetxt2tagslexer.png (even if it's for scrite, it looked similar on geany)
Now in Geany all headers are blue instead of being red, all special formatting such as **bold**, //italic//, --striked-- are in flashy blue instead of being colored in light blue, red or green, and they are all bold instead of being bold, italic or striked.
I've built geany from git and it's the same. I've also built scite from the mercurial repo, and it's still working, so I don't think the errors are from recent change in scintilla. I don't understand what is causing this new behavior in geany.
You can customize the color scheme mapping in "filetypes.txt2tags". There were huge changes to the filedefs/color schemes and it looks like for "txt2tags" the defaults are not very good. If you get it looking well, attach your "filetypes.txt2tags" to this bug report and I'll update it. There's some (less that perfect) documentation in the manual on how to edit filetypes/color schemes.
color definition for txt2tags
I see now in https://github.com/geany/geany/commits/master/data/filetypes.txt2tags "Make all filetypes.* files use named styles.", which removed all the color definitions.
I see in http://www.geany.org/manual/current/index.html#styling-section that both can be used. Is it compulsory to use only named styles? Because I don't see any equivalent to the tags used by txt2tags in filetypes.common, so I propose to revert back to the old version. Here is an attachment of it.
and btw it's the color scheme also used for the kate and scite text editors.
It's not compulsory to only used named styles but we won't revert to the old one (because of having colours hard-coded in the filetypes file), however we can certainly get it fixed. I think more named styles need to be added to the color schemes (and filetypes.common) to allow for light markup languages like this and Markdown and stuff. Patches are welcome, but we'll fix it sooner or later if not. For now I guess just continue using the one you attached.
The look changed as part of making common styles for colourschemes it isn't broken.