varl/qmk_firmware
1
0
Fork 0
forked from forks/qmk_firmware
Code Pull requests Activity
qmk_firmware/keyboards/crkbd/keymaps/nimishgautam
History
Albert Y cbabc8dbe6
[Core] Replace Tapping Force Hold feature with Quick Tap Term (#17007) 
* Replace Tapping Force Hold feature with Quick Tap Term

* Replace keyboard level TAPPING_FORCE_HOLD with QUICK_TAP_TERM 0

* Deprecate force hold in info_config.json

* Before and after quick tap term unit tests

* Quick tap unit tests iteration

* Keymap config.h correction

* Remove TAPPING_FORCE_HOLD_PER_KEY macros that were missed

* Add two more test cases for quick tap

* Replace TAPPING_FORCE_HOLD with QUICK_TAP_TERM in configs #2

* Replace TAPPING_FORCE_HOLD_PER_KEY with QUICK_TAP_TERM_PER_KEY in configs #2

* Add function declaration for get_quick_tap_term

Co-authored-by: Stefan Kerkmann <karlk90@pm.me>
2022-12-12 16:52:22 +01:00
..
config.h [Core] Replace Tapping Force Hold feature with Quick Tap Term (#17007) 2022-12-12 16:52:22 +01:00
keymap.c Fix some old keycodes (#19086) 2022-11-15 16:52:01 +00:00
readme.md [Keymap] corne layout with mac/linux text editing shortcuts (#18374) 2022-09-30 16:07:20 -07:00
rules.mk [Keymap] corne layout with mac/linux text editing shortcuts (#18374) 2022-09-30 16:07:20 -07:00

readme.md

Full-featured Corne layout for Linux and MacOS

This is a generic layout for Corne, especially for someone who:

  • has to type in English
  • occasionally has to type in Swedish
  • Switches regularly between Linux and MacOS
  • Prioritizes text navigation
    • This includes selecting whole lines and deleting words
  • uses VIM or VIM bindings for text navigation
  • uses the 'compose' feature in Linux and uses the 'mac user dictionary' trick for getting compose features
  • Home row modifiers for optimal ergo (hopefully optimal)

This also features:

  • OLED displays:
  • indicating OS and LED status (scroll lock, numlock, caps, compose) on the master side
  • layer and modifiers on the slave side
  • LED lights:
  • color changes to indicate layer and modifier status
  • LED matrix effects around keypresses

Major notes

OS 'detection'

  • I assume MacOS as the default. Using the ctrl/gui swap magic keycode switches everything to Linux
  • Most of the Linux codes should work in Windows
  • Yes, there are lots of if-statements around which key code to send here... this isn't the most sustainable way to do it, but is the most memory-efficient way I could come up with

RGB matrix effects

  • Not all RGB matrix effects are compatible with changing the color on layer/mod change. Some of them get caught in a loop and freeze half of the keyboard, so beware of which ones you activate
  • Some RGB settings are stored in eeprom (despite me using the noeeprom() version of functions) If something is weird, try clearing eeprom
  • The color-changing function probably should be in the layer_state_set_user function, except that function doesn't give the state of the modifiers. So instead I have it done in a call that updates the OLEDs

LED state explicitly not shared

  • For some reason, sharing the LED state (as a split keyboard function) will cause the slave side of the keyboard to freeze up if you type too fast. Don't do it!

Windowing shortcuts

  • Again, MacOS is assumed to be the default so I changed as many Linux shortcuts as I could to make them compatible with MacOS. Some of them don't have default shortcuts defined (such as 'move window left' or 'launch calculator') so I just made those as needed

Right-shift preferred

  • At the time of this writing, left-shift wasn't always being registered as a modifier key when checking modmasks, so I stuck with everything using right-shift as it had the expected effects

Compose key