20100613 is out. There are a few auto-indentation related fixes, the major one being that ctrl+v is now a plain paste, rather than pasteAndIndent. There are some situations where pasteAndIndent will never be able to do the right thing, so it wasn't a great choice for the default behaviour.

I've also dusted off some old project functionality, so there's now an option to view the project in a tree view on the left, which can be activated via the View/Project Panel menu. The tree control itself is fairly clunky, but it should be a reasonable stop gap.

Excellent. You kept the "tab adds lots of indentation", which I love.By the way, what did you mean by "When there are multiple bindings for a command, the most recent is displayed, rather than the first"? Displayed where?

Did you change something in the rendering code? I expect the problem is on my end, but still it is worth asking:

The DirectX mode now always displays blurry when I launch Sublime Text, and maximizing/restoring twice in a row does not fix it (after a single maximize/restore it looks okay, but after the second one it returns to being blurry; resizing by dragging the border of the restored window helps; maximizing/restoring, restarting Sublime Text and maximizing/restoring again also helps), and in past I have experienced this once and switching to OpenGL eliminated the issue, but now the OpenGL mode is unusable at all. I have taken a screenshot of each mode: DirectX and OpenGL. (In the OpenGL mode, the current line is always readable and changing the cursor changes which line is readable.)

I suppose it's been included by popular demand, but I fail to see the point of the tree view side panel, honestly. It doesn't blend well with the editor's UI. Actually, it looks completely out of place.

If I understood why people need it, I'd perhaps learn to appreciate it, but in terms of usability and experience it feels wrong.

@guillermooo: I also don't like tree views, but they do serve 3 purposes.

* Most people are much more used to them. This doesn't make them better, but it does make them a feature people dislike living without.* Tree views are much better for things having to do with exploring the project. For example, on a new project, I like to look around it to see what files there are, what the directory structure is like, etc. This makes it much easier.* Creating new dirs/files is also much easier when using a treeview.* Potentially, specifying searches on subdirs could be much easier with a treeview.

* Most people are much more used to them. This doesn't make them better, but it does make them a feature people dislike living without.

This summarizes perfectly my opinion. I don't think it's a positive thing, though... I love Sublime's design and personality, and the new tree view looks like compromising both. However, if the majority of users ask for it, then there's little that can be done about it.

* Tree views are much better for things having to do with exploring the project. For example, on a new project, I like to look around it to see what files there are, what the directory structure is like, etc. This makes it much easier.* Creating new dirs/files is also much easier when using a treeview.

Maybe I'm too used to use the command line, but these things seem to fall out of Sublime's scope at the moment. I consider it a text editor, not a file browser. In any case, I see your point.

* Potentially, specifying searches on subdirs could be much easier with a treeview.

The current search in project feature is quite solid. I think the tree view is convenient because it's familiar, so we're back to point #1. I'm not claiming that the existing features are perfect, but I'd much rather see them evolve than see the editor's become less consistent and--worse yet--more mainstream. On the positive side, this is probably a sign that it's doing well commercially.

Also, even tree views are becoming obsolete in OSes in favour of search, which is what Sublime offered up to now.

I'll try to be more constructive later by posting some ideas to add to the quick panel view and maybe even to the project panel.

The reason I use Sublime, and not some other editor (like Vim or Emacs, both of which are better at "pure text editing"), is exactly because Sublime does know what a project is. Every editor I tried lacked the "quick-open from project" panel, which is a dealbreaker for me when working on an actual project (and not just messing with the editor for the fun of it).

I spent a long time trying to get Emacs/Vim/Notepad++ to understand that I have a folder with a bunch of files, that I'd like to be able to open at will using something close to the quick-open found in Sublime. And I gave up in frustration, because they are *just* file editors. And that's just the basics, moving between files. Never mind "advanced" stuff like tagging, which is even more annoying.

What I'm trying to say is, Sublime works so well because it *does* have "project" features, it *does* understand that these aren't just scattered files thrown randomly all over my file system. That's not to say I like the new project explorer (very limited and not good looking at all), and that's not to say the "quick open" isn't enough for me. But I really hope that Sublime keeps developing in a way that's aware of the fact that I use it to manage my projects, not just edit files.

Of course, now I'm hooked on Sublime because of its other amazing found-nowhere-else features, like multiple selections. But I still wouldn't use it if I couldn't manage projects easily with it.[/rant]