There should be a command line parameter that will cause sublime to fork the process and detach from the shell when starting up. I'm often in a terminal window and want to open a file in sublime, but if it's not already started it will take over the command line until I exit it. However, if sublime is already running, it will open the file in an existing window and return control to my shell.

I'd like to have a parameter I can pass on the command line (and ultimately create an alias that contains it) that will fork and return control to my shell immediately after opening the file(s), regardless of whether sublime was already running or not.

When connecting my MacBook to a non-Apple external monitor and using it as my only display, the text is anti-aliased incorrectly.

To reproduce,

1. Connect a MacBook to a non-Apple display (I was using a Samsung SyncMaster).

2. Make sure there are no Apple displays running including the laptops monitor.

3. Quit Sublime Text 2 if it is running.

4. Open or restart Sublime Text 2.

5. Note that the text's rendering is different and incorrect from the standard rendering of text in OS X.

Some notes:

I've found that when Sublime remains open while switching between monitors the method it anti-alias' the text remains. For example, if the rendering is incorrect and I switch to a display that traditionally renders it correctly, it will remain incorrect until I quit and restart Sublime Text 2.

I prefer to use Sublime Text 2 on OS X with the gutter hidden completely. However, when the gutter is hidden, the left margin of text is a very narrow 2 pixels which is too close to the window border.

ST sets the "unsaved changes" if the file is removed from disk, even if not modified in ST. This leads to the following sequence of events:

1. open a file from removable media in ST

2. temporarily unmount the media

3. remount the media. ST now thinks it has changes to the file.

(This can also happen when switching to git/hg branches where those files are missing, or with network-mounted files that temporarily disappear when credentials expire.)

At this point ST will refuse to load actual external changes to files (e.g. when switching git branches) because it thinks it has modifications. You have to manually close every file, with a warning message about discarding alleged "changes" for each one.