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

51–60 of 113 posts

Re: ⌘Q is too damn close to ⌘W

#52

Post by bsergean »

d0m wrote: post #34

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

The unintentional F1 happens to me all the time in Vim and it pops up this annoying gnome-terminal help. I should read it one day.

Re: ⌘Q is too damn close to ⌘W

#53

Post by bsergean »

duopixel wrote: post #30

I'm willing to bet the author is either A) not a touch typist or B) Comes from Windows/Linux. It's not the author's fault, of course, but it has been around since 1984 and it's unlikely to change. The 'native' way to type commands on a Mac is using your thumb to press Command and your pinky to press Q, or your ring finger to press W. It feels awfully weird pressing Q with your ring finger. Window/Linux users use the…

I'm using Linux at work and Mac at home, so I fixed a lot of problem by using a Mac Keyboard at work ...

Re: ⌘Q is too damn close to ⌘W

#54

Post by abraham »

dedward wrote: 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".

Re: ⌘Q is too damn close to ⌘W

#56

Post by leif »

BCM43 wrote: post #15
scott_s wrote: post #10

In vi, I use control+w to shift between the sections of a split window. You can imagine the hilarity that used to ensue. But, it's not an issue anymore. I haven't made that mistake in well over a year.

Similarly, in emacs I use ctrl+n to go down. On FF, this will open 5-20 windows, depending on how long I wait. (I have a very fast repeat.) Pentadacty with emacs bindings has helped with, but occasionally I will hit the key to pass all keys to FF, and once again end up with ~20 windows to close.

Me too, ugh. I also can't tell you how many times I've hit M-d thinking I'd delete a word and then keep typing, and end up writing all over the address bar instead.

Re: ⌘Q is too damn close to ⌘W

#59

Post by andreyf »

eli wrote: post #14
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.

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

This.

Re: ⌘Q is too damn close to ⌘W

#60

Post by noahth »

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.

And if you use the Recently Closed Tabs feature on the New Tab page, you can reopen sets of tabs that were all closed at once.
Post reply on HN