This repository was archived by the owner on Oct 7, 2025. It is now read-only.
Unable to quickly review PRs due to broken keyboard #173
MFarabi619
started this conversation in
Show and tell
Replies: 2 comments 2 replies
|
Fixed. |
2 replies
|
I was so eager to view the fabled fax machine, and unfortunately I played this at full volume on my speakers in the office today... To atone for my carelessness I must now face hours of awkward silence sitting at my desk, reflecting on my mistake. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Description
Keyboards are electro-mechanical devices used to interface with other devices known as personal computers which are used by humans to speed up computation. Therefore, keyboards are classified as human interface devices.
I encountered a possible defective key switch issue on my hand-assembled split keyboard. To kick off the debugging marathon, I did
sudo pacman -Syuwhich then broke my laptop keyboard too. Therefore, I as a human(hopefully) am now currently unable to interface with my personal computer entirely.I resorted to shuffling up the switches on my split keyboard, during which I received a phone call. I made the wise decision of taking the call and ended up making the problem worse by forgetting which switch(es) were defective. I must now therefore replace the entire set and pray that this is not a PCB matrix issue; if so, then RIP me.
The key switch happened to conveniently belong to my
Ctrlkey, which is one of my most beloved keys given that I am an unfortunate Emacs doomer.Due to my keyboard-driven workflow, this is an urgent gating issue. It not only hinders my ability to review PRs, but it also affects my quality of life as I live out of Emacs. It also humbles me to remain with code and think twice before venturing into circuits.
To Reproduce
Expected behavior
My keyboard must stop not working so I can continue running into more bugs.
Screenshots

Additional context
This issue was created from my fax machine.
All reactions