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.

[Edit: This could be rephrased as: "cmd+n should do the same as File->New File when no window is open"]

Sublime portable for linux!!

It'd be great if Sublime would support vim-esque hard text wrapping (eg. 'textwidth') without having to invoke a command. The current approach, being done retrospectively, makes it more likely that weird artefacts are introduced, such as paragraphs being collapsed (when editing LaTeX, I often find lines with individual commands are collapsed into one line, breaking it in the process). Hard wrapping as-you-type would also make it easier to track changes on a line-by-line basis in version control, whereas again the current approach often leads to equivalent lines being changed in less predictable ways.

When opening large files, SB takes too long to "cache" the file.

Modern text editors should open large files much faster. Per load the inital block and do your cache in the background or some such.

I have a 300MB log file (all text). It takes about 3 seconds in Notepad++.

It takes about 30 in sublime text.