Live data from Hacker News

⌘Q is too damn close to ⌘W

squishtech.posterous.com

81–90 of 113 posts

Re: ⌘Q is too damn close to ⌘W

#81
post #14
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.

I think the Ctrl+Shift+T shortcut to reopen closed tabs works across sessions too.

This did not work for me using Chromium 5.0.375.127 (0) under FreeBSD 8.1.

Re: ⌘Q is too damn close to ⌘W

#82

Earlier quoted context omitted.

On the other hand, in Dvorak, Q is directly above the left ⌘ key (where X usually is), and W is directly above the right ⌘ key (where , usually is). I'm always reminded of this serendipitous symmetry whenever people complain about ⌘Q and ⌘W being adjacent on QWERTY.

absolutely. this is a wonderful thing...i may close a lot of windows, but i don't usually quit the entire program unless i mean to.

unless somebody steps up to my computer and tries to cut some text

Re: ⌘Q is too damn close to ⌘W

#83
post #54
post #38

Most browsers warn you if you are about to close multiple tabs.... I guess chrome doesn't? Weird. That would be an implementation problem for chrome - every other OSX application tends to properly warn you if you are about to close multiple context windows with cmd-q. EDIT: Just researching a bit- this seems to be a conflict between the Chromium design goals and the OSX UI guidelines... the Chrome team absolutely ref…

The latest developer version of Chrome (9.x) has an experimental warning dialog in "about:flags".

Where? I have 9.0.570.1 on Windows 7 (32-bit) and I don't see such an option in the about:flags.

The only flag relating to tabs I can see is the first one to put the tabs down the side.

Re: ⌘Q is too damn close to ⌘W

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

Re: ⌘Q is too damn close to ⌘W

#85
post #54

Earlier quoted context omitted.

The latest developer version of Chrome (9.x) has an experimental warning dialog in "about:flags".

Where? I have 9.0.570.1 on Windows 7 (32-bit) and I don't see such an option in the about:flags. The only flag relating to tabs I can see is the first one to put the tabs down the side.

The flag is "Confirm to Quite". It might be Mac (v 9.0.572.1) only right now as I don't see it in Linux (v 9.0.570.1).

Re: ⌘Q is too damn close to ⌘W

#87
German hackers represent: On a German keyboard on Windows or Linux, you have to enter a few characters with the right Alt key (the "AltGr" key). This includes the "@" sign, which is located on the "Q" key. A lot of first-time switchers thus cause their browser to close every time they try to enter an email address.

Incidentally, the "@" sign, as many other characters, is on a different key on the German Mac layout. Never understood why e.g. the US layout stays the same on every system, but the German one doesn't. Good time that I switched to the US one long ago. Now I only have to fight with different ways to access umlauts…

Re: ⌘Q is too damn close to ⌘W

#88
post #13
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.

Well yes, but if you have 20+ tabs open in a couple of windows, it's disruptive and time consuming to close and reopen all of them.

why not use sessioin buddy[0] plugin, which save your tabs, so you don't have to open 20+ all at once

[0] https://chrome.google.com/extensions/detail/edacconmaakjimmf...

Re: ⌘Q is too damn close to ⌘W

#89
well, this is not really a solution to his problem, but instead intended as an informational bit. i am actually using a dvorak(-programmers) layout. then the Q and W keys are quite far apart, with the Q key right above the left ⌘ key, and W right above the right ⌘ key, a really handy addition to an (already) awesome layout.

Re: ⌘Q is too damn close to ⌘W

#90

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).
Post reply on HN