<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On Mar 29, 2006, at 11:01 AM, Charilaos Skiadas wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><DIV>On Mar 29, 2006, at 2:58 AM, Trevor Harmon wrote:</DIV><DIV><BR></DIV> <BLOCKQUOTE type="cite"><DIV>The thought of all that redundancy bothers me; perhaps there's some way of "subclassing" the XML language type? Or is there an entirely different way to handle this kind of thing?</DIV> </BLOCKQUOTE><DIV><BR></DIV><DIV>It's called:</DIV><DIV><SPAN class="Apple-tab-span" style="white-space:pre"> </SPAN>include='text.xml';</DIV><DIV>just create a new language with this in its patterns, that should do it, I think. You could even override some of the scopes to get finer results, if desired.</DIV></BLOCKQUOTE><BR></DIV><DIV><SPAN class="Apple-style-span">Interesting; that works, but only if I put it in the XML bundle. If I try to put the QEL language definition into its own bundle, then<I> </I>TextMate starts thinking <I>all</I> XML files are QEL files. (Is this a bug or a feature?)</SPAN></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Also, include='text.xml' only seems to work for the patterns field. I find that I have to cut-and-paste the XML definitions of folding*Marker, firstLineMatch_disabled, and repository into the QEL language definition, instead of just including them. Or am I missing something? Thanks,</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Trevor</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>