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

Add samuel's literate keymap file for planck #4998

Merged
merged 13 commits into from
Feb 15, 2019
Merged

Conversation

asamwow
Copy link
Contributor

@asamwow asamwow commented Jan 29, 2019

Description

Added my awesome keymap written in a .org file for emacs users mostly. This way, you can easily edit your keymap in the org mode table, and changes will be reflected in the actual tethered keymap file. No more having to maintain comments and balancing tables to have a neat config file.

The actual keymap is not that important, just allowing other's to easily create their own keymaps in org if they wish. But if you are interested in the keymap, it is heavily based on a standard dvorak layout using a single extra layer and a lot of custom implemented tap keys to make it all work. It feels amazing!!!

Types of changes

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

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).

@asamwow
Copy link
Contributor Author

asamwow commented Feb 4, 2019

Hello, please take as long as you need for this PR, but I just wanted to communicate that my last commit addressed issues raised in @drashna 's review. Please tell me if anything still needs to be looked at again, thank you.

Additionally, the commits get squashed if it gets accepted right? When I made those commits I didn't expect to make this PR so I couldn't imagine them being very useful to anyone.

@drashna
Copy link
Member

drashna commented Feb 5, 2019

The only remaining issue is a coding convention (formatting) one. As is, it's pretty hard to read. If you're fine with that, then that's okay.

And yes, we squash keymap PRs, like this.

@asamwow
Copy link
Contributor Author

asamwow commented Feb 12, 2019

I am fine with the formatting. I and other emacs users if they so choose to use this keymap will never look at the keymap file, but only at the org file. Thanks!

Copy link
Contributor

@mechmerlin mechmerlin left a comment

Choose a reason for hiding this comment

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

Great!

@mechmerlin mechmerlin merged commit d04485e into qmk:master Feb 15, 2019
dlhextall pushed a commit to dlhextall/qmk_firmware that referenced this pull request May 24, 2019
* added my own keymap

* changed thing

* updated keymap Samuel

* updated laypout for better one handed use

* updated stuff I want

* happy with my lagout

* formatting

* Added new literate config

* made everything nice

* cleaned

* fixed spelling and two small bugs in macros

* Made press and lift function for modifiers
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.

3 participants