QMK_V8
Custom QMK Keymap for Keychron V8 (by semicharmed)
qmk-keymap
My keymap & reusable QMK gems (by getreuer)
| QMK_V8 | qmk-keymap | |
|---|---|---|
| 1 | 40 | |
| 1 | 255 | |
| - | - | |
| 6.8 | 6.1 | |
| 7 months ago | 7 days ago | |
| C | C | |
| MIT License | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
QMK_V8
Posts with mentions or reviews of QMK_V8.
We have used some of these posts to build our list of alternatives
and similar projects.
qmk-keymap
Posts with mentions or reviews of qmk-keymap.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-12-05.
-
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 =)
What are some alternatives?
When comparing QMK_V8 and qmk-keymap you can also consider the following projects:
EC60 - Open source universal 60% Electrostatic Capacitive PCB.
AutoHotkey - AutoHotkey - macro-creation and automation-oriented scripting utility for Windows.
pheromone_keyboard
benign-key-logger - A simple, transparent, open-source key logger, written in Python, for tracking your own key-usage statistics.
q3_qmk - My fork of Keychron's QMK fork with my Q3 customizations
MouseJiggler - MouseJiggler using arduino pro-micro
keyboards - A split keyboard layout, optimized for Portuguese, English, working with numbers and software programming with VIM plugins.
kmonad - An advanced keyboard manager
CMD-dactyl-manuform
qmk_keymap - The keymap for my Ergodox EZ
jonkey
qmk_firmware - Open-source keyboard firmware for Atmel AVR and Arm USB families. My code will be in branches with the mkillewald prefix.