[quote=âagibsonswâ]@facelessuser
He, he, I was looking at this yesterday, and wondered why ST didnât offer the second, default, argument. But it does - must have been in my blind-spot when I glanced at the docs.
Curious as to why you created theme files, rather than just creating a dictionary? Perhaps you feel users would be more comfortable modifying the plist.
My **idiom **(notice the Python reference there?) would be to delete all the â self.bground = ââ â as they are now *always *assigned a value, but we had a similar discussion before
Are âactiveGuideâ, etc., standard pList items in ST? Or have you made them up for the plug-in? (Iâve struggled to find a list of the possible items.)
Andy.[/quote]
I just took the Monokai Bright Color Scheme file and modified it. I figured it needed to be in accordance with other scheme files. People can modify them if they want. I left everything in the settings section so it would be functional if some used it (I canât imagine people using the grayscale one though). In the gray scale one, I gutted everything scope wise because everything is black accept comments which is gray. If something was italic or something, I left it in.
âactiveGuideâ controls the color of the stippled tab guides.
People can use my other plugin and convert the plist to a JSON file if they like that better for modifications. But I wanted to be universal with how I handle all input colors schemes.