The command to wrap text at X characters should wrap only selection if one was made, instead of a paragraph. This would allow to easily wrap a comment in source code file without altering the subsequent code.

Drag files from the sidebar into a panel to open them there.

I'd like to write code matching Google's C++ style guide:

http://google-styleguide.googlecode.com/svn/trunk/cppguide.xml?showone=Function_Declarations_and_Definitions#Function_Declarations_and_Definitions

Indent to bracket mode supports this style already:

ReturnType ClassName::ReallyLongFunctionName(Type par_name1, Type par_name2,
                                             Type par_name3) {
  DoSomething();
  ...
}

In the event that the parameters are too long to fit on the line, I'd like to use this style:

ReturnType LongClassName::ReallyReallyReallyLongFunctionName(
    Type par_name1,  // 4 space indent
    Type par_name2,
    Type par_name3) {
  DoSomething();  // 2 space indent
  ...
}

performing a grep on shell/terminal will give me a file result like:

./folder1/file1.ext: .....

./folder1/file2.ext: .....

./folder2/folder1/file1.ext: .....

doubleclick on the filename will copy "./folder1/file1.ext"

perform GOTO ANYTHING shortcut in sublime and paste the filename.

nothing shows up because of the leading "./" string. you have to cut off the "./" or if grepping from subfolder just the "."

would be awesome if GOTO ANYTHING would ignore this leading pattern. Maybe ignoring just a leading "/", will be helpfully for someone too....

Resize the project panel small enough so you have a scrollbar. Scroll all the way to the right. Enlarge the project panel until the scrollbar disappears. Whoops, now all the filenames are cutoff with no scrollbar.
Small inconvenience, but I think the right edge of the content should remain anchored to the splitter until the panel becomes larger than the contents..

The following datetime-string will make give wrong syntaxhighlightning in python 2.7: "%H%M".

The last M will not be marked purple, but instead yellow like a normal string.

A picture's worth a thousand words:

In my opinion, lines with ':=' operator should look the same as lines with '=' operator. As far as I've tried, the same issue appears on every color scheme.

Valid Clojure code:

(+ 1 2)

(+ 1N 2N)

However, first is correct with the Sublime syntax file, and the second is incorrect.

Fix:

inside Clojure.tmLanguage, change the regex for constant.numeric.integer.clojure from (-|\+)?\b[0-9]+\b to:

(-|\+)?\b[0-9](|N)+\b

There might be better fixes but this atleast does not show invalid syntax :)