Hacker News new | ask | show | jobs
by jeppesen-io 1050 days ago
First glance I thought this was silly with left ctrl changed to fn

But on closer look, I saw caps lock was changed to ctrl. Which is what I do on all my computers

I hope the Framework ecosystem grows so we might someday see a keyboard like this for it

6 comments

If there were an HHKB or Tsangan layout keyboard module for Framework laptops, first party or otherwise, that'd make them significantly more appealing to me when laptop shopping. One of the main downsides of becoming a keyboard enthusiast and finding a layout that really "clicks" with you is that you're stuck with standard layouts on laptops.
For my preferred layout in QMK, I have Caps Lock mapped to Caps Lock only on tap, and Control on hold. I also have the right Alt key mapped to Backspace on tap, Alt on hold, to give me an additional backspace which I can hit with my thumb, keeping the rest of my fingers on the home row.

http://www.keyboard-layout-editor.com/#/gists/4d894ef5848c4f...

I use kmonad[1] to have QMK-like functionality on any keyboard.

https://github.com/kmonad/kmonad

> I saw caps lock was changed to ctrl. Which is what I do on all my computers

But then how do you yell at people on the internet?!?!

BOTH SHIFTS TOGETHER TURNS ON CAPS LOCK and tap either to turn it off.
The new framework keyboard is QMK so it shouldn't be a problem
And no CapsLock at all. Bug or feature?
If you need capslock that’s easy to emulate in software nowadays. For instance KDE has a default option to toggle capslock by pressing both shift keys.
I use that, but unfortunately it's not that easy (also I'm pretty sure it's not KDE-specific - most keyboard stuff even works in the console!).

Let's use `xev`'s `state` field for reference:

First, `state & 0x10` is NumLock which is the only modifier that's often set. Software knows to mask out this and a couple other modifiers when dispatching keyboard shortcuts.

Second, `state & 0x02` is CapsLock. Software that detects CapsLock as a modifier will work correctly with double-shift-as-capslock.

Unfortunately, `state & 0x01` is Shift. Software that reads CapsLock as a keysym (often e.g. games that use it as a "turbo" toggle) will often fail, because when double-shift is pressed, the shift modifier has been set. And it's generally considered a bug to ignore modifiers when dispatching keyboard events.

Unfortunately, there is no event for just "`state` changed", it is only dispatched alongside some other mouse/keyboard event. If you press just `shift` you'll see that it doesn't update yet for the just-pressed key (and fundamentally cannot due to how it has to work to switch between keycode->keysym mappings).

In my entire computing career, I have never locked my Caps or unlocked my Num! That's how I roll.
Only hit caps lock on accident. I used to pry the CAPSLOCK keycap off my keyboards at work.
Definitely a feature. All the "lock" keys are bugs.
I've had CapsLock mapped to Esc for years and haven't looked back. I'm OK with holding Shift.