Shayne Holmes 48ff93582b Pull out sendstring variations to their own files.
Instead of having all sendstring keycode mappings in the main quantum.c
file, give each one its own file in keymap_extras that can be #included
in a user's keymap. If one is included, it will define the appropriate
lookup tables and overwrite the weak definitions in quantum.c.
(Including more than one sendstring definition will fail at compile
time.)

Update @rai-suta's test keymap to match, as well as the documentation.
2017-07-05 10:55:47 -04:00
..
2017-06-11 22:16:42 -04:00
2017-06-11 22:16:42 -04:00
2017-06-11 21:24:23 -04:00
2017-06-11 22:16:42 -04:00
2017-06-11 22:16:42 -04:00
2017-06-11 21:24:23 -04:00
2017-06-11 22:16:42 -04:00
2017-06-11 22:16:42 -04:00

How to add your own keymap

Folders can be named however you'd like (will be approved upon merging), or should follow the format with a preceding _:

_[ISO 3166-1 alpha-2 code*]_[layout variant]_[layout name/author]

* See full list: https://en.wikipedia.org/wiki/ISO_3166-1#Officially_assigned_code_elements

and contain the following files:

  • keymap.c
  • readme.md recommended
  • config.h optional, found automatically when compiling
  • Makefile optional, found automatically when compling

When adding your keymap to this list, keep it organised alphabetically (select list, edit->sort lines), and use this format:

 * **folder_name** description

List of Planck keymaps

  • default default Planck layout
  • cbbrowne cbbrowne's Planck layout