Adding folding and `entity.name.tag.block.any.html` `support` for `section`, `article`, `aside`, `header`, `footer`, `nav` and `menu`
Added a command to update includes across the project or selected files.
Reassign TM_DIRECTORY when processing the file so #relative# is calculated properly.
Support new name for Firefox binary from 7.0
Fix escaping for Avian.

The escaping rules for TextMate is “only escape characters that has meaning in current context”. When the backslash is followed by a character that has no special meaning then that backslash is a literal backslash.

The 1.x snippet parser was a two-pass parser, first parsing the snippet syntax, and then parsing the potential format strings in transformations, meaning that the initial pass would treat ‘/’ as having special meaning while extracting the format string even though the format string “changes context”.

Being compatible with 1.x is problematic since we may nest format strings, e.g.: ${1/.*/${0/\b\w/${0:/upcase}/g}/} — if we generalize the two-pass parser rules to support arbitrary nesting then we would need to do arbitrary passes and for each pass, we’d (likely) remove one set of escapes.
Scope empty braces in embedded source.

This is to override the default behavior of pressing return.

Hopefully we’ll find a better long-term solution for how to provide this feature without hardcoding it in TextMate but also without having to add rules to every single grammar out there…
Add web preview command.
Remove PHP bits and pieces.
Add readme.
Make doctype match case insensitive, improve firstLineMatch.

Patch initially from Paul Miller.
Remove ruby embedding bits.
Updating syntaxes as per this gist https://gist.github.com/gists/1386199/ to add support for new HTML5 elements, validity of numbers in ids and unquoted attribute values.
Move folding settings.
Don't mark < in comments as invalid.
Fix exception presumably introduced with Lion.

The checkbox in the nib previously resulted in a string or integer being stored in the property list returned. We used `to_i` and compared it with `1` for “maximum flexibility”.

Now an actual boolean is found in the property list, and as the boolean does not implement the `to_i` method, an exception was thrown.

This fix has not been tested on 10.6.
updating input snippet with new drop down options
drop down for different media types
Only use “current word” if it looks like a tag.

This is done by matching against /^[\w\-:_]+$/i. In practice current word would only contain a dash, underscore, or colon, if the character classes for the document type has been redefined to make that part of the word character class or if the command is invoked with a selection.

This change was made to avoid an issue when using the command in a location like: <p>‸</p>, here “current word” would be “></”.

Also enable UTF-8 so /\w/ matches non-ASCII word characters.
Add initial semantic classes.
Improve pasting indent expectations with indentOnPaste setting.