I have a hard time noticing which files are unsaved vs saved.  I was wondering if you could make it more obvious when a file has yet to be saved.

Would be nice to move the deleted file to the Trash (Mac) and prompt before delete, some thing like "Are you sure?"

a live php syntax checker would be nice, just like in RapidPHP 2010

It would be nice if lines I've modified, as measured against my RCS (e.g. git) would be marked in some way--for example, by changing the color of the margin (or line number) for that line.  Different colors could be used for adds, deletes, and modifications.

Many Python projects use either reStructuredText (sphinx) or epytext (epydoc) formatted docstrings.  It would be very nice to have syntax highlighting on those docstrings.

The project specification and the project state should be stored separately (maybe sublime-project and sublime-workspace?). As it is now, it will be difficult to edit the project files (because there is so much state information stored there) and sharing projects doesn't make much sense. The simplicity of the old project files was great but I really like the features of the new projects. Can't we have the best of both worlds? sublime-project (build_system, folders, save_all_on_build, plus any include/exclude instructions). sublime-workspace (buffers, file_history, find_in_files, find_state, groups, layout, select_file, show_minimap, side_bar_visible, side_bar_width, status_bar_visible)

"It may be worth doing this, but I'm concerned about confusing people: people may not know what a 'workspace' is, so they use the project functionality when they'd be better served by using workspaces." http://www.sublimetext.com/forum/viewtopic.php?f=2&t=1444&p=6606#p6623

Sublime Text "internally" manages the state information for other aspects of the editor ("Auto Save Session", "Session"), so why not store the project definitions "externally" and the current state (workspace) "internally"?

By storing these separately, people could more easily share projects and could still have their own local workspaces.

The biggest issue I can see is the possibility of the project and the workspace getting out of sync (if one of the files is moved to a different location).

I often use TextMate to write a quick Python script, run it, collect the output, and throw it away. In these cases, I never save the file. However, in Sublime Text 2 I have to save the file before I can run the Build command. It would be great if it automatically created a tmpfile for untitled/unsaved docs and ran the Build command on that.

I should be able to pipe output on the command line to sublime_text. Sublime should wait until end of file is reached, open a new file, and copy the contents to the new file.

When opened file was modified externally ST2 makes Revert and looses the scroll position. It makes impossible to watch for the log files changes if it is being periodically updated externally. Scroll position should be restored after the file refresh.