News for hackers. Stuff that matters.
Re:Splash screens == sloth by roadnottaken on Monday February 20, 2012 @11:08AM (#3612778)
I guess this is sort-of the idea behind OSX behavior where an App is running with no open windows. They WANT you to leave everything running in the background. As a longtime Windows user, I still find this confusing, but I think they're trying to make everything appear to "load" instantly because it's just always running... sort of like on a phone.
Re:Splash screens == sloth by jlarocco on Monday February 20, 2012 @12:38PM (#3613097)
At first I didn't like it, but I've eventually started to really like this in OSX. Having a ridiculous amount of RAM to "waste" may have helped change my mind. My only gripe is that I wish it were a per application setting.

Some apps, like my browser, mail program, the terminal, Emacs, ... I love having start quickly, even if it's because they were just in the background before.

Other stuff, like Preview, I don't use often enough to care about the load time, and I would probably configure it to exit when the last window closed.

Re:Splash screens == sloth by openbear on Monday February 20, 2012 @01:09PM (#3613222)
>> Other stuff, like Preview, I don't use often enough to care about the load time, and I would probably configure it to exit when the last window closed.

Under Lion, that is (sort of) what Preview and TextExit do. When you close all open documents in Preview and then switch away from the app, the app will terminate.

Re:Splash screens == sloth by tikhonj on Monday February 20, 2012 @02:53PM (#3613615)
For Emacs, you should consider using Emacsclient and server. That way it's always on in the background, takes a fraction of a second to open a new window and shares state between all the different windows. Additionally, it lets you configure programs that use an external editor, like Git, to just open a new buffer in your current Emacs session, which is very convenient.
Re:Splash screens == sloth by why-el on Monday February 20, 2012 @11:26AM (#3612829)
+1. I find that extremely annoying. Some times I reopen a window of preview let's say just to close the whole program.
Re:Splash screens == sloth by msbarnett on Monday February 20, 2012 @01:59PM (#3613396)
Why not just switch to it and quit it without opening a new Window?

That's the whole paradigm. Windows belong to applications, but applications aren't windows. That's one reason the menu bar is divorced from any window (along with Fitt's law): so that you can interact with an app even when it currently has no windows open.

Re:Splash screens == sloth by pavel_lishin on Monday February 20, 2012 @01:13PM (#3613241)
> Some times I reopen a window of preview let's say just to close the whole program.

I do not understand what you are saying. Can you elaborate?

Re:Splash screens == sloth by why-el on Monday February 20, 2012 @08:47PM (#3614826)
Here is a scenario, and my mac is a month old, so maybe I am borrowing heavily from Ubuntu and MS experiences. When I am reading two pdfs, and then close one, it makes sense for the preview menu to stay on because I am reading the second pdf, but when I close the second, what reason is there for preview menu to stay up?

Edit: As to my original comment, when I switch to another app, preview stays open, but up to now I don't know how to close it because I can't get the menu to appear without a pdf or something using it, that's why I reopen a document, forcing the menu to show up, then close the app.

Re:Splash screens == sloth by pavel_lishin on Tuesday February 21, 2012 @02:34PM (#3617734)
There's lots of reasons for the menu to stay open; the simplest example is clicking File, then Open, to open a new file.

As far as the menu disappearing when you close both documents, that's confusing and directly contradicts what you typed earlier. I can open Preview.app, and it'll just show me the menu. I can close it by alt-tabbing to it and hitting Cmd-Q - no windows required.

Re:Splash screens == sloth by chc on Monday February 20, 2012 @12:55PM (#3613170)
You know you could just close it from the Dock or application switcher, right?
Re:Splash screens == sloth by kylebrown on Monday February 20, 2012 @06:03PM (#3614350)
Yes but that requires a click-and-hold, causing the whole dock to resize for the pop-up menu, which is quite slow on my 32-bit MBP maxed out at 2GB RAM. I find it quicker to just click the Preview icon (causing a new window to open as the focus switches), and command+q.
Re:Splash screens == sloth by msbarnett on Monday February 20, 2012 @07:02PM (#3614502)
You might want to try command-tabbing and quitting.

Basically with command held down the entire time, hit tab until Preview is framed, and instead of releasing command (which would pull Preview to the foreground), hit Q, which will send Preview the command-q event and cause it to quit.

Re:Splash screens == sloth by masklinn on Monday February 20, 2012 @04:03PM (#3613915)
> Some times I reopen a window of preview let's say just to close the whole program.

You could just close it from the dock you know. Or switch to it and command-Q immediately.

In fact, I don't even understand how you'd go around to "reopening a window" of preview, preview will not open any window without a document in it, do you open a document just to close preview or something?

Re:Splash screens == sloth by daed on Monday February 20, 2012 @12:46PM (#3613128)
If you don't have any windows open in the app, doesn't Lion quit it for you?
Re:Splash screens == sloth by wmf on Monday February 20, 2012 @03:34PM (#3613781)
Only apps that are written that way.