Currently if I have a large code. I'm separating it by comments and indentations to fold them later.

For example:

// Views

... some views code here ...

// Models

... some models here

Would be better if there would be some codes for folding, to avoid indentation at some point of hierarchy.

For example:

// Views fold_start_1

... some views code here without indentation at all ...

// fold_end_1

Now you can fold all the code between fold_start_1 and fold_end_1.

Ofc folding codes could be shorter, it's just as an example

I have been programming in Tcl for Alpha on Macs for many years.  It had very complete API, similar to the ST2 one.  TextMate came with this very short API based only in environmental variables, but with those genial ideas. In that case the programming language was totally free, since TM is based in external scripting.  And now ST2.  It obliges you to script in Python.  I didn't know Python, although read a lot about and programmed a bit on it.  But each time I dig into the ST2 API to program on Python… I miss Ruby so much!  Please, try Ruby!  Give it an opportunity.

It is a general, widely known practical observation that (at least some) people will leave (at least some of) their software preferences unchanged after installation.

Upon installation, the preference whether newlines are ensured at EOF on save is false.

This installation default is wreaking a small degree of havoc with programmers using versioning systems including git.

The reasonable and usual practice of software in Unix and elsewhere is to expect, and to maintain, that all lines end with a newline. This includes the final line. For more information, here are two links:

http://stackoverflow.com/questions/729692/why-should-files-end-with-a-newline

http://slashdot.org/comments.pl?sid=165492&cid=13808398

To be more precise, after installation, in Default/Preferences.sublime-settings these statements occur:

  // Set to true to ensure the last line of the file ends in a newline
  // character when saving
  "ensure_newline_at_eof_on_save": false,

This should be changed instead so after installation automatically the statements are:

  // Set to false to ensure the last line of the file does not end in a newline
  // character when saving
  "ensure_newline_at_eof_on_save": true,

Further, the editor must not display a new empty line after saving as it does now when this preference is set to true. This even though there is a final newline.

The editor may be treating newlines erroneously as line separators and not correctly as line terminators. This possibility is described in the links above.

Alternatively, you could implement a Close All Saved Files option. 

For project settings it would be nice to be able to define "files" as well as "folders".  Sometime there are files that might exist outside of a directory.  Rather than including an entire folder only to exclude all but one or two files it would be nice to be able to just include specific files.  This could take many of the same parameters as the folders, name, path, etc.  Of course the exclude patterns wouldn't make sense to include.

Example:

{
    "files":
        [
            {
                "path": "/path/to/my/file.txt"
            },
            {
                "path": "/path/to/my/other/file.txt"
            }
        ]
}