Maybe it's a version thing, but Ctrl+Shift+T doesn't work for me. Cmd+Shift+T does. But will it restore all the tabs you had open when you accidentally quit?
I've had this happen to me in Chrome a few times recently (I switched to Chrome full time a few weeks ago), but I've never had it happen in Safari since Safari prompts you if you have multiple tabs/windows open.
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.
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.
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.
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.
I forget where I saw this tip, but after making this mistake several times I remapped command-Q in Chrome to the "Zoom" command. (Keyboard control panel -> Keyboard Shortcuts -> Application Shortcuts). It's already saved me lots of time. And of course, any harmless menu command will work in place of "Zoom."
Edit: after I RTFA, I see this is much like what the article suggested. The only real difference is that my approach prevents you from quitting from the keyboard at all.
That's the one feature that's definitly missing from Safari. (Safari only just now learned to re-open the last tab with Command-Z. All the other tabs you'll have to search for yourself in the recently closed pages-menu.)
In addition to the "reopen all windows" option mentioned you would probably be wise to check out the Sessions safari extension if you tend towards my habit of keeping lots of state in tens of browser windows with lots of tabs in each window... Sessions does a much better job of actually remembering your open tabs and windows (I have had the LastSession plist get messed up and windows or tabs open up completely empty too many times to count) and you can create or edit various save points for collections of windows and tabs.
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.
...and then posting a nice hack to relocate the nostrils to the top of the head during Cheerios-eating time and sidestep the spoon-nostril problem entirely. So it's not so bad.
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.
Switchers to OS X with a german keyboard layout also experience quite a lot of fun. That's because on Windows, you have to type ALT+Q to get the @ in an email adress.
You have to fight your muscle memory not to type CMD+Q in OS X.
That's why for applications that I do not want to quit easily I set "Application (keyboard) Shortcuts" [ OS X ] to require something less commonly used (like cntl-opt-cmd-Q) for quitting. [ OS X System Preferences -> Keyboard ]
Just to name two: I heard Colemak is nice, and I also tried learning Neo for a while. (Neo is especially suited for German.) I am using Dvorak at the moment.
Oh, I do. Same with C-z as mentioned below. When I'm in a terminal-based session, I keep C-x C-c and C-z around. When I'm in my main X-based session, C-z is zap-to-char and C-x C-c is bury-buffer.
you just changed one of the consistent features of all os x applications, how to close applications and close windows/tabs of applications.
for some reason i always use the finger motion/press of thumb on left ⌘-key + index finger on q key to quit things and i've never experienced the ⌘q ⌘w issue.
I think squishtech's first clue that they changed one of the consistent features of all OSX applications was when they went to the control panel and changed the feature.
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 pinky to press ctrl, taking your hand out of the usual touch typing position, and thus making it more prone to mistakes.
I agree with your premise but not your conclusion. I'm a touch-typist - but many touch typists in the computer age end up not always using classical touch typing methods - after all,the traditional typewriter keyboard didn't have an alt or cmd or ctrl key, right?
I use the thumb on left-cmd and a ring finger on either q or w (never thought about it... maybe I use the pinky sometimes) - and I don't recall ever making a mistake, although I suspect that may partially be because I primarily use safari, and it warns me if I try to close multiple tabs or a single tab/window with form data filled out.
And everyone should hopefully be mapping capslock to ctrl.... that just saves all kinds of hassle down the road.
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'.
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
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.
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.
I think that the best approach would be do have a warning as default, except from in "Incognito" mode - that way, people who feel a need to quickly close the browser can use Incognito mode or disable the warning and the rest of us avoid troublesome accidental closing of the browser.
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.
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 people at Apple really hated that idea, so after some lively debate they settled on ⌘⇧Q instead. (As a bonus, it's now a global shortcut, so you don't have to be in Finder to use it.)
Similar problem with web browsers. You can give it a different shortcut, or you can enable a prompt to warn when closing multiple tabs. Most people opt for the latter.
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.
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
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.
In System 7, I think it was, it was possible to use ResEdit on the Finder to add a ⌘Q. Useful if you were low on memory. IIRC, if the last application exited, the Finder would restart.
112 comments
[ 1.7 ms ] story [ 169 ms ] threadI initially thought Cmd+Shift Q would be better, but that is tied to System Logout.
Edit: after I RTFA, I see this is much like what the article suggested. The only real difference is that my approach prevents you from quitting from the keyboard at all.
[0] https://chrome.google.com/extensions/detail/edacconmaakjimmf...
http://dl.dropbox.com/u/8247646/sessions/index.html
+1
You have to fight your muscle memory not to type CMD+Q in OS X.
http://www.codinghorror.com/blog/2010/03/the-opposite-of-fit...
Just to name two: I heard Colemak is nice, and I also tried learning Neo for a while. (Neo is especially suited for German.) I am using Dvorak at the moment.
(I would do this myself, but I keep putting it off.)
for some reason i always use the finger motion/press of thumb on left ⌘-key + index finger on q key to quit things and i've never experienced the ⌘q ⌘w issue.
I think it'll be OK.
It feels awfully weird pressing Q with your ring finger.
Window/Linux users use the pinky to press ctrl, taking your hand out of the usual touch typing position, and thus making it more prone to mistakes.
I use the thumb on left-cmd and a ring finger on either q or w (never thought about it... maybe I use the pinky sometimes) - and I don't recall ever making a mistake, although I suspect that may partially be because I primarily use safari, and it warns me if I try to close multiple tabs or a single tab/window with form data filled out.
And everyone should hopefully be mapping capslock to ctrl.... that just saves all kinds of hassle down the road.
However, I've pressed f1 instead of escape a couple of time so I make sure to bind f1 to escape in vim
If you're using Firefox you just make sure browser.warnOnQuit is set to True (out of the box, it's set to true.)
As far as Chromium goes, near as I can tell ctrl-Q does not work at all, which is something Firefox would do well to imitate.
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.
The only flag relating to tabs I can see is the first one to put the tabs down the side.
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.
Apps: double tap
Windows: Good idea! If only there was an OS that treated those as vital UI components...
I would really love to have a consistent set of shortcuts across emacs and everything else I use.
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 people at Apple really hated that idea, so after some lively debate they settled on ⌘⇧Q instead. (As a bonus, it's now a global shortcut, so you don't have to be in Finder to use it.)
Similar problem with web browsers. You can give it a different shortcut, or you can enable a prompt to warn when closing multiple tabs. Most people opt for the latter.
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.
defaults write com.google.Chrome NSUserKeyEquivalents '{"Quit Google Chrome"="@$Q";}'