ssm.expand_css_constants now *always* reports failed substitutions. How did we stylesheet devs ever live without this??
For example, the lists are completely different when simulating a load from the Themes menu, which tells me that the theme-related dictionary lookup is broken. This trace could be disabled, but imo we may as well leave this for now. I did make a tiny change to the substitution logic itself. It now excludes '@button', '@constants', '@data', '@language' from the list of symbols to be substituted. These can appear in comments and I see no way excluding them could be a significant change. The alternative would be to exclude them from the *reports* of failed substitutions, but I think the present code is good enough. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
