20100924 is out now, with a collection of improvements. It's still not much more usable for editing tasks - I'm focusing of fleshing out the structure first. It should start to get more useful once the Python API is enabled (many editing commands, including ctrl+backspace and ctrl+delete rely on this), which I'm currently expecting to happen after projects and session support, which are the next targets.

There's a quick panel in this version, which can be used to switch between open buffers. It works differently to the one in Sublime Text: where as Sublime Text will filter items, X will both filter and reorder them. This makes it much nicer to work with on large projects, which you'll get to see when projects are exposed in the near future. The quick panel itself is still a work in progress - most of the time so far has been spent ensuring that it's fast on large projects (i.e., 50k+ files), and that the ranking gives high quality results.

As an aside, I'm quite happy with the side bar and view resizing in this version - it has detents to help stop the resize at a nice spot (as long as you're not moving the mouse quickly), and the resize areas can be double clicked to resize them directly to the detent.

I'm not sure if you are taking suggestions / ideas, but I was thinking that it might be nice to have the possibility to filter the contents of the side bar (in the case when many files are open or when you only want to consider a subset of the open files). Maybe a keyboard shortcut could give focus to a input box at the top of the side bar and the contents of the side bar would be filtered in the same way as the quick panel (but without the sorting). This would be different than the "Select Buffer" option (using the quick panel) in that the filtered file list in the side bar would persist until the filter was cleared.

I imagine that you will be adding projects (maybe with the latest "session" for that project) to the side panel as a separate top level node (at the same level as "Buffers"). If this is the case, I think it would be helpful to be able to filter the side bar contents, which would allow you to have a view of the matching files across multiple projects or sessions (including the current session).

jbjornson: I was originally considering implementing the quick panel entirely as filtering in the sidebar, but abandoned that in favour of the current approach, so that results could be ranked. I imagine it wouldn't be unhandy to have filtering in the side bar in addition to the quick panel, but the quick panel would generally supersede any side bar filtering?

Actually, there's a good argument to be made for placing the current quick panel in the side bar directly, filtering results with ranking. I'll look into it again when project support is up and running.

jbjornson: I was originally considering implementing the quick panel entirely as filtering in the sidebar, but abandoned that in favour of the current approach, so that results could be ranked. I imagine it wouldn't be unhandy to have filtering in the side bar in addition to the quick panel, but the quick panel would generally supersede any side bar filtering?

I think the quick panel filter would have to supersede any side bar filtering. Maybe you could default the quick panel filter to be the same as any existing sidebar filter and allow the user to edit that filter.

I created an alias to launch sublime X from bash on OSX, and it seems to try to open the file, but always complains that is can't open the file format.

BTW, I was looking for where session information is stored along with packages, but can't seem to find anything. I would assume they would go into ~/.sublimetextx or something similar? That is what most other editors/apps do configuration data on unixy systems.

Overall though, things are looking good. Glad to see the start of the QuickPanel!

The dot files are common on Linux/Unix. Although MacOSX is indeed a Unix system underneath, configuration files are usually stored somewhere in ~/Library or ~/Library/Application Data. That is for user settings. For all users you would follow /Library or /Library/Application Data. It is similar but still different enough. For unix application ports the normal "dot" files are used (i.e. vim, emacs etc.), so in reality it is a mixture of both.

In the first file it is mentioned that the user should create the file User File Type.sublime-options to override the default values (which is the default behavior until SublimeText 1.4)I tried that on MacOSX but it does not seem to override the values in MacOSX File Type.sublime-options (i.e. in its current state only the font)Jon, should this be that way? Meaning that the same way that Default File Type.sublime-options will be ovewritten in a software update, I guess that the same will happen for the OS specific ones. So changing the options on the Mac specific options file will be valid until the next update.

Can we have complete control over the bindings precedence in Sublime X? ZenCoding bindings, by virtue of Z > G, overriding my G)enshi snippets is a little frustrating.

I'll be focusing on getting the key binding system up to speed in next weeks release, and I'll get that sorted at the same time. Not quite sure what form it'll take, but perhaps just the ability to specify a priority number per-package, and sorting on that in preference to the package name.