⌘Q is too damn close to ⌘W • Hacker News Board

Re: ⌘Q is too damn close to ⌘W

#31

Post by jemfinch » Tue, Nov 09, 2010, 3:56 AM UTC

uxp wrote: post #27

Janteh wrote: post #21

Earlier quoted context omitted.

Chrome actually reopens all tabs for you if you use the command after restarting chrome. I don't like the author's solution because I use cmd 1-9 for navigating between tabs.

I don't like the author's solution either. Cmd+Option Q seems like an unused alternative that wouldn't require a major re-wire of habits to change to, just a slight mash of the keys to the left. I initially thought Cmd+Shift Q would be better, but that is tied to System Logout.

Ah, that must be why there's the inconsistency between Mac and other platforms here. On Windows and Linux, Ctrl-Q does nothing; Ctrl-Shift-Q exits Chrome.

Re: ⌘Q is too damn close to ⌘W

#32

Post by jemfinch » Tue, Nov 09, 2010, 3:57 AM UTC

glhaynes wrote: post #23

alunny wrote: post #13

Earlier quoted context omitted.

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.

And I'm sometimes a little annoyed at all the things to which I've been saying for the last week "I'll get back to that" suddenly showing up in my company's proxy logs all at once.

If that's a serious concern you might want to rethink your company ;)

Re: ⌘Q is too damn close to ⌘W

#33

Post by tedge » Tue, Nov 09, 2010, 3:58 AM UTC

With a bit of practice, you can train your hand to do ⌘-W as a 3-finger "chord" by touching your middle finger to the 'Q' key before allowing your index finger to depress the 'W'.

Re: ⌘Q is too damn close to ⌘W

#34

Post by d0m » Tue, Nov 09, 2010, 3:59 AM UTC

In theory maybe but in practice I've never typed cmd+q instead of cmd+w. (A little bit like I've never typed ctrl+a (which select all) instead of ctrl+s (which save)).

However, I've pressed f1 instead of escape a couple of time so I make sure to bind f1 to escape in vim

Re: ⌘Q is too damn close to ⌘W

#35

Post by drivebyacct2 » Tue, Nov 09, 2010, 4:02 AM UTC

I will give plenty of karma to anyone who can tell me an easy way of doing something even remotely similar in Linux. I'd love it.

Re: ⌘Q is too damn close to ⌘W

#36

Post by wmoxam » Tue, Nov 09, 2010, 4:04 AM UTC

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.

Many sites use session cookies, which expire on exit.

Re: ⌘Q is too damn close to ⌘W

#37

Post by sp4rki » Tue, Nov 09, 2010, 4:10 AM UTC

slig wrote: post #8

Latest chrome (9.x dev) has an option in "about:flags" to show you a kind of confirmation box before quitting.

This has been the best tip I've ever gotten. Thank you kind sir for having changed my life so drastically in just a second!

+1

Re: ⌘Q is too damn close to ⌘W

#38

Post by dedward » Tue, Nov 09, 2010, 4:14 AM UTC

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 refuses to add a warning dialog if you try to close multiple tabs, but it would be the expected behaviour on OSX.

I tend to fall on the side of OSX - part of what makes it great is UI consistency - and this is one case where Chromium is making things worse, not better.

Re: ⌘Q is too damn close to ⌘W

#39

Post by miguelrios » Tue, Nov 09, 2010, 4:14 AM UTC

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.

That doesn't change the fact that I get mad and lose time whenever I accidentally close all my tabs.

Re: ⌘Q is too damn close to ⌘W

#40

Post by megrimlock » Tue, Nov 09, 2010, 4:17 AM UTC

What's really needed here is not more distance between hotkeys, but instead universal lightweight undo for user interactions.

The most precious resource is the user's time. There should be no interaction that irreversibly discards the user's work. We have fairly universal undo for editing operations; there should be just as much undo support for closing windows, tabs, or apps -- carefully constructed artifacts of the user's workflow.