Dev Build 2088

[rdougan]

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..

[rdougan]

@jps

I've noticed that if you do CMD + T and try and use your keypad to navigate up/down, it does not function correctly. You need to type something first for it to work (even space works).

CMD + R does not have this problem.

[natebeaty]

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.

[bradgessler]

I agree with speby, but let me put a use case around it:

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.

[buymeasoda]

Is it just my setup, or does the "goto anything" grow wider as you type in the text field?

I loaded the default theme, opened the box with CMD+P, started typing and it gets larger horizontally with each keypress.

Anyone else experiencing that behavior?

[jps]

Is it just my setup, or does the "goto anything" grow wider as you type in the text field?

It does indeed - will fix for the next build.

I'll also add a setting to disable lion style full screen for the next build - I have to maintain two ways to use full screen in any case, for 10.6 compatibility

[lunixbochs]

I love lion's fullscreen on my air, but I agree I don't think I'd like it as much on a dual-monitor setup. maybe apple will fix it.

[natebeaty]

I'll also add a setting to disable lion style full screen for the next build - I have to maintain two ways to use full screen in any case, for 10.6 compatibility

Great news! Thank you.

[oats]

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.

[jps]

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.