I discovered an issue with AsyncProcess::read_stdout() and read_stderr() in exec.py: If for some reason os.read() returns a split UTF-8 sequence the decoding will fail.

I found this by having a custom build system running g++ on a remote machine over Putty's plink.exe

Not being proficient in Python the fix I use is to simply buffer up the returned data:

    def read_stdout(self):

        buf = bytes()

        while True:

            data = os.read(self.proc.stdout.fileno(), 2**15)

            if len(data) > 0:

                buf += data

            else:

                if len(buf) > 0 and self.listener:

                    self.listener.on_data(self, buf)

                self.proc.stdout.close()

                if self.listener:

                    self.listener.on_finished(self)

                break

I've only noticed this behaviour once in Mountain Lion 10.8.2, but Sublime Text  2.0.1 (Build 2217) suddenly started ignoring the setting

"open_files_in_new_window" = true

Restarting the editor did not solve the problem.

The behaviour was fixed by setting this option to false, then back to true again.

I was not doing anything special at the time, so don't really know how to reproduce the bug. Hope this helps someone!

• open files in read-only mode (should be controlled thru command line)
• in full screen mode (can be added as Sublime setting or as command line option)

Sometimes I close the build results tab and want to open it again. If I want to jump to a build error, I obviously want it open.

Easier solution: Is there a way to bind keys to "Show Build Results" (haven't found it..)