The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Qmk-keymap Alternatives
Similar projects and alternatives to qmk-keymap
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
keyboards
A split keyboard layout, optimized for Portuguese, English, working with numbers and software programming with VIM plugins. (by rafaelromao)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
benign-key-logger
A simple, transparent, open-source key logger, written in Python, for tracking your own key-usage statistics.
-
qmk_firmware
Open-source keyboard firmware for Atmel AVR and Arm USB families. My code will be in branches with the mkillewald prefix. (by mkillewald)
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
qmk-keymap reviews and mentions
-
Is it possible to have a magic key for same finger skipgrams?
Yes, it is technically possible in QMK to record a history of the previous 2 keys (or more) to have a skipgram-reducing magic key. This is possible in QMK by saving the keycode for each event in a sliding buffer. See my example on triggering based on previously typed keys and the source for my Sentence Case for implementations of such a key history buffer. I see u/mEFErqlg shared an implementation as well in another comment thread.
-
Designing a Symbol Layer
I really appreciate all the work that's going into ZMK, and am by no means an expert on the limitations or architecture that they're working within, but personally feel that the recent macro-parameter implementation fails to elevate the Behavior[3] into a sufficiently powerful construct. I'm trying to imagine how it could offer greater composition and control over an invoked sequence of keycodes, key-positions, and behaviors, but if that ever comes to be, it will be on the shoulders of giants. Development has been very active, and the contributers have all done great work. Shoutout to zmk-nodefree-config[4] and thumbkey[5] for android, which has also been under rapid development from a wide group of contributers (special thx to WadeWT and sslater11, amoung many others).
[1]: https://github.com/getreuer/qmk-keymap/
-
Thumb and modifiers
Check out my keymap. My intention is to put a rather light load on the thumbs. Lately I've been doing this:
-
Q2 SEVERED RGB ANSI Encoder (knob) keymap with separate RGB settings for Mac/Win mode, RGB indicators for Caps Lock and Fn Layers, Caps Word, and Autocorrect!
Uses getreuer's 400 entry autocorrect dictionary. https://github.com/getreuer/qmk-keymap/blob/main/features/autocorrection_dict_extra.txt
-
Favorite Macros and Other Keyboard Configurations (on VIA or otherwise)
A cool thing with QMK is that you may insert arbitrary C code to handle key events. That's a lot of power, and I've been having fun with that. Check out my keymap. Some gems:
-
Sentence Case: QMK feature that automatically capitalizes first letter of sentences
Please pull or re-download getreuer/qmk-keymap to get the latest.
- Heavily documented QMK mechanical keyboard keymap
-
Why are people suggesting 65% layout for office?
I am a software engineer and use a 65% as my daily driver. 65% is enough for the most common keys including a number row on the a base layer, and I have special symbols and F-keys on a symbol layer (see my keymap). For me, the point of mechanical keyboards is ergonomics, and on that front I suggest a split, columnar keyboard with QMK or other programmable firmware. Here is a brief features tour of why I think these keyboards are so awesome.
-
How much time do you spend using your mechanical keyboard and what types of activities do you use it for?
I'm a software engineer and naturally spend a lot of my time at the computer writing code, plus quite a bit of non-code writing (emails, reviews, ...). Since RSI is something of an occupational hazard, mechanical keyboards are for me mainly about preventative ergonomics and comfort. Though, writing custom code within QMK keymap has interesting productive possibilities... I've been having fun with that.
-
kc_pwr?
You want fun experimental features?—check out my QMK repo =)
-
A note from our sponsor - WorkOS
workos.com | 28 Apr 2024
Stats
getreuer/qmk-keymap is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of qmk-keymap is C.
Sponsored