Be aware that if you do it too often, the pause goes away. I don't even think anymore about putting "sudo" in front of whatever I'm doing because I simply do it so often. And 99% of those are legitimate - my day job requires root access for significant portions of my code to operate, while even my home computer, I'm the obvious sysadmin, so I'm zipping around the linux boxes with a sudo ever at the ready to solve my or my wife's issues.

That said, given the risk/reward ratio, the low number of times it happens, the small amount of effort it takes to undo currently, and the ill effects of such a mistake, I wouldn't think there's enough downside to the current system to warrant a discussion about a better system. I'm sure there is such a better system out there, but having been convinced that "the perfect is the enemy of the good" - this system is "good" enough, we don't need to tweak it into the perfect. Just my $0.02CDN

Huh?!? In theory, that's right. In practice it becomes a habit. And when you make a habit of it the "root pause" still does exist, but progressively sees its power decrease. I am very careful when I do something potentially risky. But sometimes I happen not to realize that something is risky at all! Fortunately this happens rarely enoug, but it happens, as stupid as it may look like: for example when I mv'ed a file over my mailbox on a certain account.

However I get the point: it seems that approximately half of the people thus far agrees with me that as humans (as opposed to Gods) we can fail and we should have a second chance, and another half believes that errors are rare enough and remedies are easy enough to take that we should stick for KISS sake with the current behaviour. That's fine for me. I only want to explain that one reason why I didn't think of the CB is that... ehm... I'm not familiar with it. Really I don't even like it. In fact I have it disabled. Can I just

/msg janitors Oops! I considered [id://123456] by mistake, please unco
+nsider it!
[download]

in case of necessity? Or should I explicitly turn it on?

By all means, turn the CB on to msg someone, then turn it off after you've chatted with the Senior Person In Charge to explain yourself (if necessary). I think the CB is a neat distraction, but I like to see it; and I understand others may not want to see it. I found the Users Currently Logged In node (or whatever it's called) to be very distracting, and hence I deleted it from my view. That's the beauty of being able to configure the site the way you want it.

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

You don't have to turn the CB on and then off again. Just go to fullpage chat or new java chat client (to name just 2 of many available alternate clients) when you need to chat.

- tye        

I have the CB nodelet enabled in all views, but perpetually /chatteroff. That way, I can still see and respond to direct /msgs, but without the distraction of the chatter itself.

---

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Me too. I wrote "disabled" by lack of proper lexical richness/confidence with the precise jargon. Indeed I do have the CB enabled in /chatteroff mode both to /msg users (and be /msg'd) and to be alerted when replies to my nodes are posted. Sorry for any misunderstanding my bad wording may have created...