Skip to content

docs(keymap.c): fix typos #93

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.

Sign up for GitHub

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

Open
arthurzenika wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(keymap.c): fix typos #93

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions qmk/keymap.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,10 +83,10 @@ const uint16_t PROGMEM keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
};


// This is where you’ll write most of your custom code for your keyborad.
// This is where you’ll write most of your custom code for your keyboard.
// This callback is called right before the keycode is sent to the OS.
//
// returning false cancels any furnther processing.
// returning false cancels any further processing.
// for instance, calling `tap_code(KC_B)` if KC_A is pressed but true is
// returned, "ba" is sent, but if `false` is returned, it’s just "b"
bool process_record_user(uint16_t keycode, keyrecord_t* record) {
Expand Down Expand Up @@ -125,7 +125,7 @@ bool process_record_user(uint16_t keycode, keyrecord_t* record) {
}

static inline bool tap_keycode_used_in_text(uint16_t keycode) {
// We can’t make assumptions on curstom keycodes
// We can’t make assumptions on custom keycodes
if (keycode >= SAFE_RANGE) return false;

// Remove "quantum" part of the keycode to get the action on tap.
Expand Down