Ahh...see I *knew* I was missing something obvious. Thanks.
It's a little strange though that some HTML bundles (like control- shift-W) work fine in Plain Text mode, but control-shift-L doesn't. That's what was throwing me off.
------------------------------------ Todd Dominey :: Dominey Design http://domineydesign.com/ http://slideshowpro.net/ http://whatdoiknow.org/
On Aug 10, 2006, at 8:39 AM, Todd Dominey wrote:
Ahh...see I *knew* I was missing something obvious. Thanks.
It's a little strange though that some HTML bundles (like control- shift-W) work fine in Plain Text mode, but control-shift-L doesn't. That's what was throwing me off.
you can expand the scope of that command simply by appending a comma to the scope selector. This will add a blank scope to the snippet, making it available in every scope (with the lowest possible specificity, so any other commands / snippets with that binding will take precedence, assuming they're in scope.
http://macromates.com/textmate/manual/scope_selectors#scope_selectors
Not exactly certain if the expanded scope on ctl-shift-W is intentional or not, but since that behaviour makes sense in a number of cases (well, really all the xml-related contexts), I'd be inclined to believe it's intentional. If not, it's a serendipitous mistake.
On 10/8/2006, at 16:54, Jeremy Amos wrote:
Not exactly certain if the expanded scope on ctl-shift-W is intentional or not, but since that behaviour makes sense in a number of cases (well, really all the xml-related contexts), I'd be inclined to believe it's intentional. If not, it's a serendipitous mistake.
It is indeed done deliberately. There’s a few commands deemed useful in all contexts (with lowest precedence) which then has no scope selector. The Mail and Xcode bundle also has a few of such commands.
-
Allan Odgaard -
Jeremy Amos -
Todd Dominey