forksand
/
qmk_firmware
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
qmk_firmware/keyboards/iris/keymaps/s1carii/readme.md

10 lines
573 B
Raw Normal View History Unescape

New Pok3r Based Keymap (#3226) * Create keymap.c Modified the default to be way more like a pok3r, already clear that it needs a better ctrl location. * Delete keymap.c * Create keymap.c Modified the default keymap to be more like a pok3r, clearly needs a better ctrl location and probably some other tweaks. * Add files via upload * Update keymap.c Parenthesis correction. * Parenthetical cleanup Forgot one... * Mods and numpad; cleanup Rework mods and numpad layer, remove superfluous declarations * comment define devlayer * Create readme.md Background and intention. * Updated to fit example * Update readme.md * Update rules.mk * Update config.h * Updated includes Replaced: #include "iris.h" #include "action_layer.h" #include "eeconfig.h" With: #include QMK_KEYBOARD_H * Update rules.mk Removed RGB enable declarations * Update rules.mk * Update keymap.c Spaced out on MINS and EQL. * Update rules.mk Removed unnecessary block. * Remove the RGB call Make would fail because of the RGB call that wasn't anywhere but here, cleaned that up from the default config. * Update keymap.c Added [ and ] since I'd forgotten them originally...
7 years ago
# Pok3r Based iris Keymap
Pok3r was what got me into mechanical keyboards years ago and what has been my daily driver since, WhiteFox and the like being always on the periphery. As such, those keybinds are what is most natural and notably not in the default keymap configuration.
Make example for this keymap (after setting up your build environment):
make iris/rev2:s1carii:avrdude
Modified URLs to point to new locations
6 years ago
See [build environment setup](https://docs.qmk.fm/#/getting_started_build_tools) then the [make instructions](https://docs.qmk.fm/#/getting_started_make_guide) for more information.