Earlier quoted context omitted.
I've seen quite a few people that, either or of habit or due to it being less error-prone to type for them, use Caps Lock for typing capital letters. Instead of Shift+letter, they'd type Caps, letter, Caps. One keystroke more, but no two keys held at the same time, which is difficult for some people. I'm sure there are superior accessibility options, but those have to be found first, whereas Caps Lock just works the…
Isn't that what StickyKeys is for?
The Joys of Unix Keyboards
51–60 of 144 posts
Re: The Joys of Unix Keyboards
#52Does anyone ever use Caps Lock? It seems like such a waste of space.
Re: The Joys of Unix Keyboards
#53> I can't imagine why anyone thought Caps Lock should have had this prominent of placement. Caps Lock was originally Shift Lock on typewriters, and was adjacent to the Shift key because it was literally a mechanical locking device to hold the Shift key down.
Very much about keyboards today is derived from strange quirks that were part of typewriters for very good reasons, but have never been properly reevaluated once they were converted to electronical keyboards. Of course, the main goal likely has been to minimize friction for those users that were already used to typing on a typewriter.
Nonetheless, having switched to an Ergodox EZ about a year ago, I get more and more frustrated by standard keyboards and I'm wondering why ortholinear keyboards are not the default by now. Similarly, I find it very strange that a digital interface like USB HID doesn't allow the keyboard to specify unicode codepoints instead of key codes that then still have to be interpreted by the OS.
That is, of course I understand how we ended up where we are, but I'm constantly amazed by how conservative IT can be in some respects while changing on a dime in others.
Re: The Joys of Unix Keyboards
#54> I can't imagine why anyone thought Caps Lock should have had this prominent of placement. Caps Lock was originally Shift Lock on typewriters, and was adjacent to the Shift key because it was literally a mechanical locking device to hold the Shift key down.
Fun fact: Some home computers had both caps lock and shift lock.
Re: The Joys of Unix Keyboards
#55Does anyone ever use Caps Lock? It seems like such a waste of space.
Re: The Joys of Unix Keyboards
#56Earlier quoted context omitted.
I've seen quite a few people that, either or of habit or due to it being less error-prone to type for them, use Caps Lock for typing capital letters. Instead of Shift+letter, they'd type Caps, letter, Caps. One keystroke more, but no two keys held at the same time, which is difficult for some people. I'm sure there are superior accessibility options, but those have to be found first, whereas Caps Lock just works the…
Isn't that what StickyKeys is for?
Re: The Joys of Unix Keyboards
#57> I can't imagine why anyone thought Caps Lock should have had this prominent of placement. Caps Lock was originally Shift Lock on typewriters, and was adjacent to the Shift key because it was literally a mechanical locking device to hold the Shift key down.
Although you're absolutely right, I still think there's actual merit in the way of thinking of the sentence you're quoting. Very much about keyboards today is derived from strange quirks that were part of typewriters for very good reasons, but have never been properly reevaluated once they were converted to electronical keyboards. Of course, the main goal likely has been to minimize friction for those users that were…
The shallow response is the simple question: What are the Unicode code points for End, Calculator, F7, and Paste? These all have USB HID usages. (-:
Re: The Joys of Unix Keyboards
#58Earlier quoted context omitted.
Although you're absolutely right, I still think there's actual merit in the way of thinking of the sentence you're quoting. Very much about keyboards today is derived from strange quirks that were part of typewriters for very good reasons, but have never been properly reevaluated once they were converted to electronical keyboards. Of course, the main goal likely has been to minimize friction for those users that were…
There's a deep and complex answer to your point about Unicode code points, which is an interesting question to consider in light of the 1980s shift away from a terminal I/O paradigm. The shallow response is the simple question: What are the Unicode code points for End, Calculator, F7, and Paste? These all have USB HID usages. (-:
True; OTOH, there already are control characters such as `BS`, `DEL`, `BEL` and so on that also don't make all too much sense if you look at unicode just as a collection of glyphs. So, I personally would still maintain that allocating a couple of blocks for stuff like this wouldn't hurt that much.
Also, no one said that the HID specs could not describe a superset of unicode (e.g. transmit letters with a unicode prefix and control signals normally (or something similar)). It's just that the way things are now is about the worst case in a lot of ways.
But: As things work good enough, they likely won't change for a long time, so going on about it certainly is futile, too ;-)
Re: The Joys of Unix Keyboards
#59Every keyboard I've ever used I've remapped the caps lock to control, whether in hardware (like on my pok3r) or in software (on my work computer). I have a hard time ever using a keyboard without this remapping done.
Capslock is an Escape key for me because I use Vim a lot. I've heard lots of tmux users map it to Control and then configure tmux to use Ctrl+a as the activation mapping, which sounds very useful too.
Now my capslock is Ctrl. I find that combo to be particularly effective for me.
Re: The Joys of Unix Keyboards
#60Earlier quoted context omitted.
There are many ways to rebind caps lock to be escape on press and control when used in combination with another key. Karbiner elements on macos and xcape on Linux come to mind immediately. But some keyboard firmwares are programmable enough to do it themselves too. However. What I found best as a vim user was to use ^[ as escape. It has the added bonus of actually being faster to process by vim too.
You don't need any extra software to map Caps to Esc on X11: Just enable the caps:escape option. In context: https://github.com/majewsky/system-configuration/blob/6c4478...
My xmodmap file has things like:
! Make Caps Lock be Escape and Scroll Lock be Caps Lock
remove Lock = Caps_Lock
keysym Caps_Lock = Escape
remove Lock = Scroll_Lock
keysym Scroll_Lock = Caps_Lock
add Lock = Caps_Lock
After reading this post, I also reverted backspace and bar/backslash: keysym BackSpace = backslash bar
keysym backslash = BackSpace
[1] https://wiki.archlinux.org/index.php/XmodmapEDIT: xmodmap link