Dev Build 2088 is out now. Primary changes are Lion style full screen support on OS X 10.7, and a raft of theme related changes.

This should be it for new features before the next regular build is out, so I'm keen to know of any issues with this build (or any outstanding regressions from recent dev builds).

Changes to the theming system that will effect existing themes:

No controls have a 'background_color' property any more, instead they use the normal system of layers. This will require changes (e.g., replacing background_color with layer0.tint, and setting layer0.opacity to 1).

panel_control is no longer used for overlays, instead they now have a dedicated overlay_panel class, which will need to be in the theme. Border issues with overlay controls have also been resolved.

There are additional rules for 10.7 style overlay scroll bars, which will need to be integrated into existing themes (namely the use of the 'dark' attribute).

sidebar_tree, quick_panel and auto_complete now have a dark_content property, which should be set based on the color of their contents. This will control if light or dark overlay scroll bars are used.

New things to theme, which won't break existing themes:

sidebar_container is themeable, which can be used to add a border to the side bar

minimap_control is themeable, which allows the color of the viewport rectangle to be changed

Themes can override widget settings in a clean manner, by providing a file named 'Widget - Foo.sublime-settings' for a theme named Foo.

ok, i have two minor points, not really bugs though.- It is not possible to switch from distraction free mode to fullscreen mode. - The minimap has no shadow when word wrap is checked with a defined word wrap column which is outside of the viewport. Lets say the word wrap column is 100 but there are only 80 columns visible.

Thanks for this new release. As I somehow switched to Lion, i really appreciate your last changes.However, there is any chance of making brackets customizable (add a background, change colors on active scope etc) ?

A regression that happened a few builds ago, when Sublime reloads a file it sends the buffer back to the beginning rather than staying in place. This makes it a bit of a hassle when monitoring log files while debugging.

This should be it for new features before the next regular build is out

In your blog you said that support for Versions, Resume and auto-save in Lion would come eventually, so I was wondering if your statement above means these features won't come before SublimeText 2 is released or does it mean these features will come through the dev channels after you release a new beta?

The Lion fullscreen functionality Apple introduced sucks. The simple "fill the screen" approach, although not the official Lion fullscreen approach, was wayyyyy better than it is now. I propose moving the fullscreen mode back to the way it was and discontinue Lion's fullscreen support.

The Lion fullscreen functionality Apple introduced sucks. The simple "fill the screen" approach, although not the official Lion fullscreen approach, was wayyyyy better than it is now. I propose moving the fullscreen mode back to the way it was and discontinue Lion's fullscreen support.

The Lion fullscreen functionality Apple introduced sucks. The simple "fill the screen" approach, although not the official Lion fullscreen approach, was wayyyyy better than it is now. I propose moving the fullscreen mode back to the way it was and discontinue Lion's fullscreen support.

Odd. I think Lion implementation is much better. Having your own space is great, and you can move back to normal mode by moving the cursor to the top. The main issue right now is multiple monitor support for spaces..

As a Lion user, I have to say I'm not a fan of switching to the OS's fullscreen mode, primarily because I work with two monitors, and it's pretty much useless in that configuration.

The old fullscreen mode was much better for a few reasons:

you could cmd-` between two projects in fullscreen mode

you could have ST2 in fullscreen on monitor 1 and your File Manager/FTP app in monitor 2 (or Netflix streaming .. or Terminal)

the transition between fullscreen and non-fullscreen wasn't a full second of sliding, oozing, fading fullscreen animation (I'm on a 13" c2d mbp, not so speedy)

more I'm sure, this was just in the first 5 seconds of trying to use it...

I've never been a fan of Spaces on OS X, and shoehorning apps-as-fullscreen in as a Space seems to be fine for work on your MacBook, but we dinosaur powernerds on 24"+ dual screen setups are left out of the equation.

Maybe this is behavior we'll see fixed in 10.7.1, but I doubt it. And I'm sure maintaining two types of fullscreen mode in ST2 would be as much of a pain as it would be confusing for users.

When I use Sublime Edit, I have iTerm open filling up one screen and Sublime Edit open filling another screen. Unfortunately OS X Lion doesn't include support for multiple full-screen applications at the same time (each on its own screen) so my only option is to use the Sublime Edit "classic" fullscreen functionality.

Unfortunately iTerm also switched over to the Lion fullscreen API, so also now see titlebar at the top of the screen when I "fill screen".

I could see a few options for this: (1) sublime edit has a multi-pane terminal interface similar to iTerm that I could use to fill the alternate screen or (2) have some sort of way to enable the "classic" fullscreen mode again.

One regression I noticed with the last few builds on OS X:With nothing selected, I used to be able to quickly duplicate a line by cmd-C and cmd-V. On Windows, when I paste the duplicated line, it always generated a new line for me, no matter where the caret was. On OS X, it will paste the duplicated line wherever the caret is, e.g. in the middle of the existing line. I don't know if that was intentional, but I really liked how it worked in Windows.

On OS X, it will paste the duplicated line wherever the caret is, e.g. in the middle of the existing line.

Not so much a regression, just a not-implemented-yet thing - it's always been this way on OS X and Linux. I'd like to support this eventually on these platforms, but it's not high on the priority list atm.