Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added my Prime_O Layout #4811

Merged
merged 11 commits into from
Jan 10, 2019
Merged

Added my Prime_O Layout #4811

merged 11 commits into from
Jan 10, 2019

Conversation

oliviahanley
Copy link
Contributor

Description

Just adding in my personal keymap for the Prime_O.

Types of changes

  • Core
  • Bugfix
  • New Feature
  • Enhancement/Optimization
  • Keyboard (addition or update)
  • Keymap/Layout/Userspace (addition or update)
  • Documentation

Issues Fixed or Closed by this PR

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document. (https://docs.qmk.fm/#/contributing)
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

#define ECTL LCTL_T(KC_ESC)
#define ALLM ALL_T(KC_MINS)
#define SCLS LT(3, KC_SCLN)
#define ______ KC_TRNS
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use 7 spaces instead of 6, you won't need to define this as including QMK_KEYBOARD_H already defines it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be updated! Thanks!

@mechmerlin
Copy link
Contributor

Merging this in now. Just a one last note.

I noticed you're using your master branch to submit the changes. I would recommend creating a different branch off of master, making your changes there, and submitting through that branch. If on your next QMK submission you continue editing your master branch, you'll run into some issues.

Here's a quick summary of some Git basics: http://rogerdudler.github.io/git-guide/

@mechmerlin mechmerlin merged commit ebbc372 into qmk:master Jan 10, 2019
rhruiz pushed a commit to rhruiz/qmk_firmware that referenced this pull request Jan 11, 2019
* initial prime_o commit

* Cleaned up comments, other things.

* Update bakingpy 4x12 keymap and add test mode for debugging/development (qmk#4810)

* Keymap: ave-63's iris layout (qmk#4812)

* Updated keymap to use standard seven-underscore KC_TRNS notation

* initial prime_o commit

* Cleaned up comments, other things.

* Updated keymap to use standard seven-underscore KC_TRNS notation
rseymour pushed a commit to rseymour/qmk_firmware that referenced this pull request Mar 13, 2019
* initial prime_o commit

* Cleaned up comments, other things.

* Update bakingpy 4x12 keymap and add test mode for debugging/development (qmk#4810)

* Keymap: ave-63's iris layout (qmk#4812)

* Updated keymap to use standard seven-underscore KC_TRNS notation

* initial prime_o commit

* Cleaned up comments, other things.

* Updated keymap to use standard seven-underscore KC_TRNS notation
dlhextall pushed a commit to dlhextall/qmk_firmware that referenced this pull request May 24, 2019
* initial prime_o commit

* Cleaned up comments, other things.

* Update bakingpy 4x12 keymap and add test mode for debugging/development (qmk#4810)

* Keymap: ave-63's iris layout (qmk#4812)

* Updated keymap to use standard seven-underscore KC_TRNS notation

* initial prime_o commit

* Cleaned up comments, other things.

* Updated keymap to use standard seven-underscore KC_TRNS notation
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants