HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jtroo
kanata
Rust2022–2026
jtroo / kanata

kanata

Improve keyboard comfort and usability with advanced customization

16Distinct people
28Mentions
0Explicit recommenders
8.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Improve keyboard comfort and usability with advanced customization

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:02:30 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year28 dated mentions

Observed mentions: 2022-09-08 14:13:29 UTC to 2026-06-18 17:49:07 UTC.

0369122022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 11 mentions; 2 submissions, 9 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC1129
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC716
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC404

What Hacker News says

11 sources
There are several aspects to keyboard interfaces that the article does not catch: - The physical device: - The "key board": Keys that are aligned in straight lines are not aligned with your hands. - The wrist bend affects people differently and can cause strains - Physical design to lower wrist strain is an almost entirely separate research area than optimal keyboard layout. - The optimal physical input device (in terms of input bandwidth) is hand-shaped but is more difficult to make. - The layout: - This article only discusses permutations of letters for increased bandwidth and less strain. - Considering computer users can "easily" reach 80-120 wpm with QWERTY, speed is a moot point for non-competitioners. - Few people learn a new layout and have a confirmation bias when they do; real usage data is scarce
Read the rest
. Real-world experience differs slightly; e.g. I have more race conditions on Dvorak than on QWERTY because of left/right-hand speed differences. Dvorak does succeed at distributing consecutive letters between the hands, but I never had problems with accidental twiddles on QWERTY. Would you rather be fast or accurate? For most people, the trade-off is somewhere in the middle. The layout is about much more than permutations of letters. Anyone who tried to or aspires to run Kmonad, Kanata, or Neo2 or who have a window manager with custom keybindings that control their environment, or who type with more than one kind of keyboard (e.g. pinyin, cyrillic, greek), or who need to type special unicode symbols that don't have a key combo in traditional layouts (math, emoji): The bar for keyboard input is higher, and I don't know any project that attempts to unify these. My "keyboard" is a combination of many open source tools, some of which work better than others, others have a steep learning curve, yet others are only documented in foreign languages. [0]: https://github.com/kmonad/kmonad [1]: https://github.com/jtroo/kanata [2]: https://en.wikipedia.org/wiki/Neo_(keyboard_layout) [3]: https://www.neo-layout.org/
In Your keyboard layout is broken
Kanata supports early tap-hold dispatch based on key overlap, which is all I need. There's an open issue for more advanced conditions: https://github.com/jtroo/kanata/issues/128 The maintainer has been very responsive in my experience and would probably add more advanced conditions if someone wanted them. > There are way too many interactions for me to list Sounds like mostly hackarounds for non-keyboard-friendly software. I generally prefer to use keyboard-friendly software (of which there is no shortage on linux) and just make application-specific keybindings directly in each application. Anything else is inevitably a hack. Window management, browsing, anything related to text or programming, etc. all have good keyboard-friendly options. I have to use some stuff like excel and teams for work, but I'll just use the mouse more in tho
Read the rest
se cases. I don't spend a significant amount of time dealing with applications like that though, and e.g. for Teams I'd try set up a matrix bridge or just use warpd before trying anything else. Teams no longer supports linux, but for other apps that have non-customizable key shortcuts, it's definitely possible hack around that and create your own in linux. E.g. When I used to use libreoffice regularly, I set up modal keybindings that sent the corresponding chords to libreoffice. As long as I can use my editor to type anything non-trivial, I'm good. For example, you have generic software like sketchyvim on mac to essentially use vim in any input field. I don't think there's a linux equivalent that lets you essentially embed an editor like vim inside any input field, but you can use a generic keybinding to open one and then have the text sent back when you're done. A lot of the examples you list don't seem to need any app-specific or context-aware functionality (e.g. your launcher example). I don't have enough of an idea of what you actually want to know if what's available on linux would support your use cases, but in addition to the numerous basic hotkey daemons there are programs like keyszer that support application-specific keybindings ootb or hawck which is scriptable in lua and supports conditional keybindings (allowing you to script per-application keybindings). You have some context available but only what is externally available, i.e. unless the program provides some way to interact with it like a cli utility or ipc socket, all you're going to be able to do is send input to it.
In Keyd: Linux Key Remapper
Delays are a terrible solution. Looking at key overlap percentage, for example, works much better. There are a lot of other ways to make dual-use/tap-hold functionality more reliability, but lots of programs actually implement overlap checks. The kaleidoscope keyboard firmware, for example, lets you configure a minimum overlap threshold for a key to start acting as its secondary role (e.g. only have space act as a modifier when it is pressed first and is held for 70% of the time the second key is pressed). In your case, I'm not sure why you would need to roll over to other keys from escape. My shift key doubles as escape, and I don't use any delay or checks at all since I don't rapidly type escape then other keys. In any case, you could try configuring your capslock key to only act as control if it being held fully overlaps with the
Read the rest
next keypress. Not sure about keyd, but kmonad and kanata both support this (I'd highly recommend kanata). That may require changing how you type depending on the modifier, which is why more fine-grained overlap threshold checks can be useful. Relevant github issues: https://github.com/kmonad/kmonad/issues/351 https://github.com/jtroo/kanata/issues/128
In Keyd: Linux Key Remapper
Sure, all good ideas in the meantime (and you could use right-thumb cmd/alt modifier or holdSpace as a vim-like cursor mod with the home keys as cursor and with H as backspace and G and delete and I as Enter to free your pinky (qwerty-layout)) But then dvorak is obviously not the best layout for this since it wasn't designed with all of that in mind. And neither were the home row mods themselves, for example, maybe only Shift is useful in the home row, and the others aren't used frequently enough (or maybe it's better to have numpad-mod key on the home row instead of the Windows key). So I guess the focus of the layout collaboration effort could be on improving the algo/data, but instead we get a bunch of new layouts that only tackle a small(er)(and different) part of the problem without much of an improvement over he previous solutions (
Read the rest
and, more importantly, with no good way to compare them). That would only leave you with the black magic of tweaking algo weights in the end :-) P.S. There is also https://github.com/jtroo/kanata alternative to kmonad And re. homerow mod keys, it seems that there is an even better approach not relying on timings (which I think are impossible to resolve with full accuracy, though with per-key timings you can get pretty close), but that's not implementable within Karabiner, so someone had a homebrew Swift solution I haven't tried
In Making a keyboard layout

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.