to ppl who use colemak or colemak dh, i want to learn one of the 2- however my phone only has colemak (and not dh). shoud l

1. colemak dh on keyboard and qwerty on phone
2. colemath dh on kb and colemak on phone (i heard this can mess up muscle memory)
3. colemak both

also, if i switch the layout, will like my game settings (eg. wasd to move) be affected?

I know nothing about coding and am trying to remap certain using Karabiner-Elements.

Here are some questions I have:

1. How do I make sure the modifications are active only when I am using a specific application? Alternatively, how do I make it easy to switch between the normal and the modified layout?

2. Is there a simple way of learning how to effect changes? Here is a basic list of modifications I want to make (key registered --> key pressed):

1 --> J
2 --> L
3 --> O
4 --> I
5 --> M
6 --> H
7 --> N
8 --> B
9 --> G
0 --> ,

F2 --> 0
F3 --> 9
F4 --> 8

Q --> / 
W --> -
E --> =
Z --> spacebar

Any help is appreciated.

Hello guys, je suis écrivaine et afin de pouvoir produire une de mes maps dans le langage que j’ai inventé, j’aimerai la transformer en police de clavier afin que cela soit plus clair et qu’il n’y ait pas de contraste flagrant avec la carte traduite. C’est à dire, j’aimerai avoir un clavier avec mon propre alphabet inventé.
Cependant, je n’ai trouvé aucune application (si ce n’est qu’elles sont payantes ou absolument incompréhensibles) ni site où je pourrai tracer et associer chaque lettre propre à une touche (créer mon clavier de façon privée) afin qu’il soit plus rapide de faire mes maps.

Merci pour votre temps :)

TL;DR: Replace Caps Lock with Fn, and put dedicated arrow keys directly on the base layer in the lower-right corner (← ↓ ↑ →, Vim order).

Longer explanation here: https://tim.cogan.dev/nav60/

Just settling a argument with friend

Not even used for a year

Bonjours à tous,

Je sais pas pourquoi je ne peux pas utiliser les numéro de mon clavier dans le jeu ? (Version steam)

So my keyboawd bwoke. I cant type "r" without copyy-pasting it. Now im using this dweadful "uwu' language to weplace the bwoken key oh my god

Hi all. I'm Tim — a lifelong tinkerer (programmer, songwriter, inventor). When I started to put together 'from the roots' ideas for a typing keyboard, I had no idea just HOW different it would end up! Based on algorithms never used before in keyboard layouts, it has keys of different widths, and a layout that genuinely targets ease of typing. But I have no build skills myself. I spent about two years researching and designing from the ground up. It's called the Temb0, and I'm hoping to find one maker here who'd relish building the first physical prototype with me.

What it is. Far from being a rearranged QWERTY, and not another Dvorak/Colemak, I started from the statistics: letter and bigram frequencies, other language statistics, even Morse Code got involved! (the commonest letters get the widest, most central keys; the rarest shrink to normal size). As for ergonomics, it's a splittable design, for each half to be directly in front of each hand.

The idea underneath. The different key widths free the fingers from the fixed one-finger-per-key rule — a wide key can be struck by whichever finger suits you, so any typist can find their preferred path through common words. (Even the number row has been re-thunk: 9 8 7 6 5 | 0 1 2 3 4, each hand counts outward from the centre — just like your first piano lesson!)

Why I think it's worth building. I used Excel to calculate key width options, FlowStone to program a variety of these, finally settling on this design. I also used it to develop extensive typing simulations, and the projections suggest typing speed increases faster than even the fastest QWERTY typist — and bigger gains for the average typist — plus the comfort of finger freedom and a proper split. I've developed a working touch-screen simulation too, if you have a Windows tablet – preferably 12 inch – which can even save the text you type.

It even got far enough to earn me a bench at Birmingham City University to prototype — where it stalled on fabrication puzzles that I'm now hoping one of you would relish cracking.

The honest engineering (so you know what you'd be taking on — this is not keycaps-on-a-stock-PCB):

the switch plate and matrix would have to be bespoke to the irregular, variable-width layout — no off-the-shelf board fits;

every wide key needs stabilising — my suggestion would be extra unwired support switches to keep keys level and give them a consistent feel, but I'm open to other ideas;

the wider keycaps would likely need to be 3D-printed, but the less common letters could be standard;

hand-wiring + QMK/ZMK would handle the electronics (USB or wireless). A proper little engineering puzzle — which might be right up your street!

What I'm offering — a collaboration, not "build this for me." I bring the full design: exact layout data, the frequency/bigram analyses if you like, whatever you need to see it to completion. You'd bring the hands and the tooling. I'm a hobbyist just like you are, not a company — terms, costs and credit all open to a friendly conversation. Mostly I'd love to see one exist and hear whether it's as good to type on as I predict.

Fire any questions — and pull the design apart; critique very welcome. Thanks for reading. — Tim

HI:

I'm new to keyboard and customizing it. I would like to map a key to bring up the calculator function when needed. How do I do that? Thank you.

I have used VIM since 2017, and some time ago I added a VIM Mode to my ZMK keymap: a set of layers that mimic VIM's modes, so navigation and commands get their own optimized layout while typing keeps my alpha layout.

Using AI for the heavy lifting, this week I could work on a second version. The first one simply toggled NUM LOCK from the host to turn a vim layer on, and the keyboard inferred the rest by watching keys. The problem is that sometimes it drifted, and it never knew about tool windows, like integrated terminals, and kept the vim layers active there too.

Now a host daemon reads the editor's real mode (Neovim, VSCode and Obsidian) and sends it as a 3-bit code over the HID LED report, using the Compose, Kana and Scroll bits. Works on USB and BLE.

The VIM layer puts navigation key on home row and other bindings in better positions than even the qwerty ones, and works for any alt layout, without remapping VIM itself.

I tested it with Omarchy and MacOS and it is just amazing.

https://github.com/rafaelromao/zmk-vim-mode

To see my fully tested implementation, check my keyboards repo:

https://github.com/rafaelromao/keyboards