No description
Find a file
Martin Gondermann 34c8bf47a7 Move Space Caded Parentheses to own layer (#1452)
* Move Space Caded Parentheses to own layer

The space cadet parentheses where too much distracting. Therefore they are now on the function layer. I also added two more layers for also having angle brackets and curly braces on the shift keys forr better access.

Also updated the README

* Fixed SHIFT+Function key conflict

* Removed Angle Bracket and Curly Bracket layers, as they don't work corrrectly
2017-07-03 11:48:48 -07:00
docs
keyboards Move Space Caded Parentheses to own layer (#1452) 2017-07-03 11:48:48 -07:00
lib
quantum
tests
tmk_core
util fix tag increment 2017-07-03 00:23:37 -04:00
.gitattributes
.gitignore
.gitmodules
.travis.yml fix up travis script 2017-07-02 23:38:20 -04:00
book.json
build_full_test.mk
build_keyboard.mk
build_test.mk
CODE_OF_CONDUCT.md
common.mk
common_features.mk
Dockerfile
license_GPLv2.md
license_GPLv3.md
license_Modified_BSD.md
Makefile
message.mk
readme.md
secrets.tar.enc
testlist.mk
Vagrantfile

Quantum Mechanical Keyboard Firmware

Build Status Gitter Docs Status GitHub contributors GitHub forks

This is a keyboard firmware based on the tmk_keyboard firmware with some useful features for Atmel AVR and ARM controllers, and more specifically, the OLKB product line, the ErgoDox EZ keyboard, and the Clueboard product line.

Official website

http://qmk.fm is the official website of QMK, where you can find links to this page, the documentation, and the keyboards supported by QMK.

Supported Keyboards

The project also includes community support for lots of other keyboards.

Maintainers

QMK is developed and maintained by Jack Humbert of OLKB with contributions from the community, and of course, Hasu. The OLKB product firmwares are maintained by Jack Humbert, the Ergodox EZ by Erez Zukerman, and the Clueboard by Zach White.

Documentation

https://docs.qmk.fm is hosted on Gitbook and Github (they are synced). You can request changes by making a fork and pull request, or by clicking the "suggest an edit" link on any page of the Docs.