@kozakmak said in userDefineLangs for .txt:
BUT! features of different themes are not taken into account, for example, dark and light
Out of curiosity, do you really change themes or light/dark that often? Everyone I know just picks their favorite theme and just leaves it like that for normal usage. If you have a use case (other than the few minutes, hours, or days required to say, “no, I like theme/mode X better than theme/mode Y”) where you frequently change themes or light/dark, I’d love to hear it… because I’ve occasionally seen people complain about things not following theme/mode changes, but whenever I’ve asked for a use case where changing is necessary, I’ve never seen a reason that makes sense to me: maybe you will be the first. (And if I know of use cases where it’s important, either I can figure out workarounds in such situations, or if it makes sense, I could start lobbying the developers to expose new API that will give information about the theme – the Dark-vs-Light mode is now in the API, thankfully)
If you aren’t changing themes or light/dark modes, then just put in the colors that work well with your theme. If you are changing themes often, then as Ekopalypse says, there isn’t a way for the plugin to know what theme you are using for now, so you’ll unfortunately have to live with that mild annoyance of editing and saving the EnhanceAnyLexer config whenever you do change theme. (If you are changing themes enough that it goes beyond mild annoyance, maybe you should consider which is a higher priority to you: changing themes, or the custom “normal text” highlighting.)