Tyyy

Thanks, Claude31. The main problem is that there are occasionally times when it would be hecka useful to autorepeat alphanumeric keys, like when you just need to type a line of CCCCCCCCCC’s for comment blocks when maintaining legacy FORTRAN 77 programs, for example. Yeah, I know this isn’t the most common use case of Xcode, but it’s the arbitrary restricting of freedom and functionality by Xcode’s developers because they can’t envision possible use cases that is so irksome. I’m not in a rush to file a bug report because Xcode now only supports versions of macOS that have long since dropped support for the Macs that I own and use :/

What do you mean by “get[ting] the alternate key”? And avoiding accidental typing errors is IMHO a dumb reason—users could reduce the keyboard repeat rate in System Preferences if that were an issue (I have all mine maxed out since I’m hecka impatient while typing/editing). Yeah, I noticed that’s also the same when typing in this forum; which makes me wonder if the two behaviors are somehow related/originate from the same software framework at some level (WebKit? Because based on how slow and unresponsive Xcode feels sometimes, I wouldn’t be surprised if it used a bloated framework under the hood similar to the way Atom is built on Electron). Anyway, boo to the Xcode developers who made that happen. If my caps lock key weren’t broken from spilling coffee on it (which I used to swap with my control key), I’d be using MacVim :/