Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

⌘Q is too damn close to ⌘W

squishtech.posterous.com

Post reply on HN
Print view View original

101–110 of 113 posts

Re: ⌘Q is too damn close to ⌘W

#101

Post by erikano »

I'm using Firefox and Vimperator [1] with a TypeMatrix EZ-Reach 2030 [2] mapped to US-Dvorak under FreeBSD 8.1 with xmonad [3] + xmobar [4].

This means that:

- When my fingers are resting on the home row, they are on keys a, o, e, u and h, t, n, s.

- When I want to close a tab in Firefox, I press d, which is left of h.

- When I want to quit Firefox completely, I press :q.

I can't remember the last time I closed a tab I didn't want to close or exited Firefox without meaning to do so. The only problem I had for a while, was that I started "record macro" with q when I meant to scroll with j - that hasn't happened for quite some time now.

I mostly only use Chromium if I am logged in on various sites in Firefox and I need to use my server as proxy to access a web service bound to 127.0.0.1 on the server (meaning that it is not publicly accessible), while also using the sites I am logged in on in Firefox. I always quit Chromium by closing all tabs, and as mentioned by others, Ctrl+w is far away from Ctrl+q.

[1]: http://vimperator.org/vimperator

[2]: http://typematrix.com/ezr2030/

[3]: http://xmonad.org/

[4]: http://hackage.haskell.org/package/xmobar

Re: ⌘Q is too damn close to ⌘W

#102

Post by philwelch »

parenthesis wrote: post #90
thought_alarm wrote: post #47

The reason it's not normally a problem is that if you're working on a document and you hit ⌘Q (or ⌘W for that matter) you will be prompted to save your changes. However, this does become a problem in web browsers and file browsers where there are no changes to save. Apparently in the early days of OS X the NEXTSTEP guys wanted to add a ⌘Q shortcut to Finder, which would log you out of OS X. As the story goes, some pe…

In earlier versions of OS X (<= 10.3 (?)), ⌘Q when in the Finder quits it, just like any other application, which was a little disconcerting the first time you did it (by mistake).

This wasn't the case at all, at least not on stock OS X (who knows what you could enable with haxies). You could certainly force quit the Finder, but it just relaunched immediately.

Re: ⌘Q is too damn close to ⌘W

#103

Post by zandor »

shrikant wrote: post #99
thisisblurry wrote: post #91

Earlier quoted context omitted.

I'm 99% certain that this is a Mac-only option for now. It might make it's way into the other OS builds, but I don't think it is currently set up for them.

Might be a v9.0.572.1 only option, and that version seems to have only made its way to Macs as yet. Windows and Linux seem to be at v9.0.570.1 still.

I've got v9.0.577.0 running on Linux and I don't have it either.

Re: ⌘Q is too damn close to ⌘W

#104

Post by parenthesis »

philwelch wrote: post #102
parenthesis wrote: post #90

Earlier quoted context omitted.

In earlier versions of OS X (<= 10.3 (?)), ⌘Q when in the Finder quits it, just like any other application, which was a little disconcerting the first time you did it (by mistake).

This wasn't the case at all, at least not on stock OS X (who knows what you could enable with haxies). You could certainly force quit the Finder, but it just relaunched immediately.

Well, that's funny, because I'm using vanilla OS X 10.3.4 right now, and I just quit the Finder in the way that I said.

Screenshots:

http://www.alexmaslin.org/quit-finder.jpg

http://www.alexmaslin.org/no-finder.jpg

It doesn't relaunch automatically. You either have to click on the Finder icon in the Dock, or otherwise it relaunches itself if you quit all other open applications.

Re: ⌘Q is too damn close to ⌘W

#105

Post by philwelch »

parenthesis wrote: post #104
philwelch wrote: post #102

Earlier quoted context omitted.

This wasn't the case at all, at least not on stock OS X (who knows what you could enable with haxies). You could certainly force quit the Finder, but it just relaunched immediately.

Well, that's funny, because I'm using vanilla OS X 10.3.4 right now, and I just quit the Finder in the way that I said. Screenshots: http://www.alexmaslin.org/quit-finder.jpg http://www.alexmaslin.org/no-finder.jpg It doesn't relaunch automatically. You either have to click on the Finder icon in the Dock, or otherwise it relaunches itself if you quit all other open applications.

That's extremely funny, but I'm almost completely certain that's not as "vanilla" as you think it is. Perhaps it was enabled on the command line? It looks like

  defaults write com.apple.finder QuitMenuItem -bool YES
will do the trick. So perhaps you're operating from a custom com.apple.finder preferences file.

Re: ⌘Q is too damn close to ⌘W

#106

Post by parenthesis »

philwelch wrote: post #105
parenthesis wrote: post #104

Earlier quoted context omitted.

Well, that's funny, because I'm using vanilla OS X 10.3.4 right now, and I just quit the Finder in the way that I said. Screenshots: http://www.alexmaslin.org/quit-finder.jpg http://www.alexmaslin.org/no-finder.jpg It doesn't relaunch automatically. You either have to click on the Finder icon in the Dock, or otherwise it relaunches itself if you quit all other open applications.

That's extremely funny, but I'm almost completely certain that's not as "vanilla" as you think it is. Perhaps it was enabled on the command line? It looks like defaults write com.apple.finder QuitMenuItem -bool YES will do the trick. So perhaps you're operating from a custom com.apple.finder preferences file.

Yes you are right. I have absolutely no recollection of tweaking this, but it seems it has been done. (I just checked a different, definitely unadulterated 10.3.x install, and it doesn't have the Finder quit menu item.) Thanks for correcting me.

Re: ⌘Q is too damn close to ⌘W

#107

Post by edge17 »

bruceboughton wrote: post #84
edge17 wrote: post #70

I think the worst design decision was putting the print button next to the save button. I've definitely sent code files in excess of 50k lines to some unknown printer before by accident.

That's poetic justice for having code files in excess of 50k lines.

Haha tell me about it. I've seen functions in excess of 30k lines.

Re: ⌘Q is too damn close to ⌘W

#108

Post by sh1mmer »

jemfinch wrote: post #7

Do people really not know that Chrome has an option to reopen itself with the tabs you had open last? Preferences > Basics > On Startup > Reopen the pages that were open last.

This is also a list of the "recently closed" tabs in the history menu if you cmd+w instead of cmd+q.

Re: ⌘Q is too damn close to ⌘W

#109

Post by cookiecaper »

jemfinch wrote: post #7

Do people really not know that Chrome has an option to reopen itself with the tabs you had open last? Preferences > Basics > On Startup > Reopen the pages that were open last.

If you have something typed up, it may not always come back. For instance, Facebook uses javascript-y input boxes, so if you accidentally back away or close the window, the browser will not restore your content. Also, a Flash game will not save your state, etc.

Re: ⌘Q is too damn close to ⌘W

#110

Post by cookiecaper »

This has bitten me several times and it really sucks. The "Restore Tab" function doesn't restore the state of Flash applications and it doesn't restore content in some input boxes (like those on Facebook, because they are hidden by JS initially).

If you're in Private Browsing mode and this happens, you lose the whole session forever, and that just happened to me the other day. It was really frustrating. :(

Post reply on HN