In syntax definitions, actions “pop” and “set” allow to provide either the name of a defined context or to define an “inlined” “anonymous” context inplace. However, the “embed” actions only accepts the name of a defined context. Is this asymetry do to a limitation of the underlined architecture, or is it a limitation that could be lifted? When defining a custom xml-like syntax, I’m finding myself creating named contexts that I only use inside a single “embed” actions, and that would be handy to be able to inline to reduce clutter.
[sublime-syntax] "embed" action shouldallow an anonymous context as value
kingkeith
#2
typically one embeds an external syntax, perhaps you are misusing it when a simple pop will suffice?
0 Likes