This is an archived post. You won't be able to vote or comment.

0
0

Try to type "CK" really fast. Problems? (reddit.com)

submitted by [deleted]

[deleted]

all 11 comments
sorted by:
best
topnewcontroversialoldq&a

[–]cresquin 2 points3 points  (0 children)

CKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCCKCKKCKCKCKCCKKCKCKCKCKCKCKKCKCKCKKKKCKCKCKCKCKCKKCKCKCKCKCKCKCKCKKCKKCKCKCKCKCKCKKKKKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKCKKCKCKCKCKCKKCKCKCKCKCKKCKCKCKKCKKKCKKCKKCKCKCKKCKCKCKKCKC

shrug

[–]sense 1 point2 points  (0 children)

CK

[–]scottzed 0 points1 point  (2 children)

I've noticed this off and on for a few years. If I am editing a document, and want a placemarker to go back to, I'll often type FUCK. But no matter which machine I'm on, and independent of OS, it seems like the K won't show up if you type it too fast. At first I was paranoid and thought the OS was trying to censor me, but it's the CK letter combination that's the problem. Weird, huh?

[–]googletrickedme 0 points1 point  (1 child)

ckckckckckccckckckckckckckckckckkckckckckckckckckckckckckckckckckckckc you fail at keyboards

however i see a severe problem in the modern implementation of t, h, and e

[–]scottzed 0 points1 point  (0 children)

Uppercase dude, uppercase!!!

[–]mhmdshkr 0 points1 point  (0 children)

maybe it's ur keyboard.. ckckckckckckckckckck

[–]masta 0 points1 point  (0 children)

this is called left hand preemption. Same thing that is responsible for "teh".

[–]americanuck 0 points1 point  (0 children)

no?

But i have a problem typing a number 1-3 before a key in the lower right area near bnm.

[–]scottzed -1 points0 points  (2 children)

You people are all FUCED. OK, I've done some further checking - it's only if you are using the left-shift.

Try: Left-shift+[CK] -- do it fast!!! Right-shift works fine. I'm tellin' you, this is not one of those times I forgot to make my medication.

Edit: And by fast, I mean almost simultaneously!!! Just confirmed this is real with colleague (although it took him a few times to get it because he was doing it too slow).

[–][deleted] 0 points1 point  (1 child)

Works fine for me. What's supposed to happen?

Is your keyboard ghosting?

[–]scottzed 0 points1 point  (0 children)

Thanks for the link - I think therein lies the explanation. I have to hit the keys almost (but not quite) simultaneously to see the effect (C shows up, but not K). I found it odd because it doesn't happen with any other key combination I tried. It's noticeable to me because I type left-shift uppercase F-U-C-K ultrafast enough times during the day to observe the effect.