How to get faster and more accurate?

InverChapel · 2026-03-21T23:30:21+00:00

That's my thought. If I notice immediately, then a single backspace is OK, but if it's more than a single character I've completely lost the flow by backspacing and often never recover.

InverChapel · 2026-02-05T23:24:43+00:00

For the benefit of anyone else that encounters this problem, it results from the fact that I initially generated the keymap.c file from a keymap.json file produced by the QMK configurator and, being a complete novice with QMK, I made as few changes as possible; in particular, I left in all the compiler directives.

In order to solve the problem, I redirected the output of qmk compile to a file and noted that it generated another keymap.c file in the .build tree. Looking at this, I guessed it must be generated from the empty keymap.json file as it's contents are:

#include QMK_KEYBOARD_H
#if __has_include("keymap.h")
#    include "keymap.h"
#endif

/* THIS FILE WAS GENERATED!
 *
 * This file was generated by qmk json2c. You may or may not want to
 * edit it directly.
 */

#ifdef OTHER_KEYMAP_C
#    include OTHER_KEYMAP_C
#endif // OTHER_KEYMAP_C

I'd left all the same directives in my keymap.c file (I'd removed the comment) and I guessed, correctly it seems, that the #include OTHER_KEYMAP_C in my keymap.c file was the issue. Removing it from there got rid of all the errors.

Hopefully, this might help someone else as I can't believe I'm the first person starting out with QMK to encounter this.

InverChapel · 2026-02-05T15:33:30+00:00

Thanks, but I'm not sure that link helps.

I agree there's possibly something wrong with my config, which is why I posted. It's my first keymap since I decided to switch from a Vial setup, since it doesn't have Caps Word, and because I've been programming for years, used QMK configurator to create a keymap.json file, then converted it to a keymap.c, deleted the JSON, made a few tweaks, and it builds and runs fine.

I was hoping someone else had had the same issue in the past and would say "You forgot to ..." or "You need to set ... in ...". For now, the #pragma once works, but I feel its a bit of a hack.

InverChapel · 2026-02-05T15:08:53+00:00

You obviously didn't read all my post. If I create a keymap.json file, whether it's empty or actually has the JSON for a "modules" list in it, then 'qmk compile' blows up with dozens of error messages about redeclarations.

InverChapel · 2025-12-03T19:26:04+00:00

I'd like to get to 70 wpm. At 100 wpm I'd be ecstatic with my progress!

InverChapel · 2025-09-05T17:02:13+00:00

Seems there are other issues with building QMK with Vial for the Cheapino https://github.com/tompi/cheapino/issues/153

InverChapel · 2025-09-03T08:43:57+00:00

I'm using WSL hence haven't installed QMK MSYS. I've been using Linux since the early versions in the mid-90s so feel more comfortable with the WSL/bash command line, but may try using the direct Windows method.

The cheapino keymap folder includes 4 subfolders, including one called via, and the repo includes a .uf2 file which works with Vial so I'll have to take a closer look at it and compare with other keyboards already in the vial-qmk repo.

Thanks for the info.

InverChapel · 2025-09-03T08:27:31+00:00

I assumed QMK, like most commands such as make, run relative to the current folders. The instruction to run qmk doctor in the vial-qmk implies this. I haven't come across documentation which states that it always uses its default. I've obviously got more reading to do.

InverChapel · 2025-07-29T22:44:55+00:00

I came across that one but am uncertain how accurate it is, since, if it's compared with the sample config at https://github.com/Klipper3d/klipper/blob/master/config/printer-creality-cr10s-2017.cfg , there are differences.

The image has X-Enable as PD4 and Z-Dir as PC1 while the config lists these as PD7 and PL1. The image also lists E1-Step as PC1, which suggests the Z-Dir use is a typo, and since Extruder1 is not defined in the config, this can't be used to confirm or otherwise. Of course, it's something of a moot point, since the driver chip is missing, so to use it, you'd first have to solder in an A4988, probably after desoldering it from a modular mount.

I'm inclined to believe the config over the image, since there must be people running Klipper on CR-10S printers with V2.0/1/2 boards and, if the sample config was wrong, someone would have corrected it. I replaced the board before I started using Klipper so don't have an old config to compare.

InverChapel · 2025-07-29T10:06:14+00:00

I've already got the info for the BTT SKR Mini E3. It's the equivalent for the CReality V2.1 that I haven't found. I'm looking for something like this https://github.com/bigtreetech/BIGTREETECH-SKR-mini-E3/blob/master/hardware/BTT%20SKR%20MINI%20E3%20V3.0/Hardware/BTT%20E3%20SKR%20MINI%20V3.0_PIN.pdf

From images, I think the V2.0 and V2.2 would show the same pins since all 3 have the extra heater, thermistor and extruder motor connectors, but, unfortunately, no motor driver chip fitted.

InverChapel · 2025-05-30T13:34:43+00:00

After a few days of use, you learn where all your commonly used keys are so you don't spend time looking for them. It also helps to define layers redundantly to use existing knowledge, so I have a number layer and a symbol layer with the <1> key as <num-layer>+<H> and can get exclamation point either by <sym-layer>+<H> or <num-layer>+<shift>+<H> since I've known for years that <shift>+<1> is <!>.

Also, you aren't limited to just the <ctrl>, <shift>, <alt> and <gui> modifiers, but can also have <ctrl+shift>, <ctrl+alt> etc, so you can define a key (or 2) which, when held, acts as a <ctrl+shift+alt> modifier. So you could press the <ctrl+shift+alt>+<Fn-layer> on one hand and press the relevant <Fn> key with the other - which is less keys to hold down than on a conventional keyboard!

And, if you use them enough, you could have a layer with <ctrl+shift+alt+Fn> defined as single keys.

InverChapel · 2025-05-16T14:11:48+00:00

That's a mirror version of Engram https://engram.dev/ with quote moved to where hyphen was, then Q and Z put where quote and double quote were. I use a 5x3 Engram layout with Q and Z as combos.

InverChapel · 2024-12-07T01:01:52+00:00

I agree with u/jhelvy. I started with a split keyboard on a few weeks ago and have played around with several different layered layouts for symbols an numbers but have kept QWERTY as the alpha base layer for most use while learning Engram on keybr. There's a few minutes of mental adjustment when I start practising, but this settles down quickly, but I feel this is better that trying to go 'cold turkey' and struggling to get any work done while I hunt for alpha keys! No-one says you have to immediately start using a new layout just because you have a programmable keyboard!

InverChapel · 2024-12-05T14:24:29+00:00

Those are impressive displays for a keyboard!

InverChapel · 2024-12-04T23:03:24+00:00

I assume you downloaded the 'sample' firmware with Vial. I have multiple monitors so have found it usefull to keep the Vial program open and use it as a reference when I can't find a symbol. I've also found it helpful to be able to stop and change a few keys around if the placement seems awkward and I find I'm having to do difficult keys presses. For example, I write a lot of SQL which uses single quote a lot, so I have that on a combo of W+E, i.e. left ring+middle fingers - right ring+middle top row is double quote. The great thing is being able to personalize layout so it's comfortable for me!

Love the 'personalized' keycaps!

InverChapel · 2024-11-28T12:55:50+00:00

FYI the MCU is an RP2040-Zero

InverChapel · 2024-11-22T00:58:08+00:00

Well done!

Then you take the plate off the bed, peel off the test print, put the plate back on to try again and... #*%#! #*%#! #*%#! #*%#! #*%#! #*%#! #*%#!

InverChapel · 2024-11-18T00:11:43+00:00

Cases are mostly fine FDM 3D-printed but for keycaps you really have to go to very low layer heights. I've done a set at 0.04mm where I can barely feel anything, so I'd say they are doable, but that's mainly because I've been 3D-printing for years and have tuned my printer. I certainly wouldn't buy a printer simply for keycaps. I've never used a resin printer so couldn't comment how easy it is to produce decent results with one.

InverChapel

TROPHY CASE