Checkin release notes
Fix encoding names for Atari ST, GB_1988-80, and HZ-GB-2312
Remove unsupported encodings (libiconv v2.4.0)
Make buffer_t::wait_for_repair a no-op with no grammar
Update last effective tab when number of tabs change

Closes #1120
Fix typo in debug output
Workaround for Xcode 5

My interpretation: The old inline array is interpreted as an initializer list which cannot (yet) be used with Objective-C objects when ARC is enabled.

Fixes #1037
Remove a few std::shared_ptr typedefs
Don’t stack allocate space for extended attribute values

Seeing a few crashes related to this, most likely because an extended attribute holds a value larger than available stack space.
Add crash report info to code involved in a crash
Source bash_init.sh for code in snippets that have no shebang

This is consistent with TextMate 1.x behavior.

Fixes ruby.tmbundle#56
Don’t default placeholders with no default text as mirrors
Rules are (unfortunately) not const during parsing

This is because of the “included” boolean we use to mark rules to avoid collecting them twice.
Add debug output
Add two-way binding support to OakEncodingPopUpButton

Previously binding to the view’s encoding property would not update the bound object when the view changed its value.
Improve the “unknown encoding” sheet

A preview is now shown with the problematic lines highlighted.
Add naive encoding classifier
Use encoding::classifier_t when opening files
Fix re-indented paste with zig-zap selections

When selecting multiple lines, but not including the newline on the last line of the selection, TextMate still consider it a “full line” and will insert a newline when pasting, unless pasting on an empty line.

Previously the check to see if the line was empty, would not account for a non-empty but selected line, which would effectively be empty since the selected text is deleted before pasting.
Reload file using most probable charset when it changes on disk

Previously if the file had been loaded as ASCII/UTF-8 and was changed on disk to something other than UTF-8, TextMate would go into infinite loop (retrying with UTF-8). It now uses the encoding classifier to find the most probable encoding (based on learned frequencies) falling back on ISO-8859-1, if there is no candidate.

Ideally it would bring up a warning, informing the user of the problem and allowing a manual correction of character set.

Fixes #1073.