agdarsec VS klfc

I've shared my experiences, too, though I don't have specific examples. I find https://hackage.haskell.org/package/parsec-3.1.14.0/docs/src/Text.Parsec.Prim.html mush easier to read, modify, and use than https://github.com/gallais/agdarsec/blob/master/src/Text/Parser.agda . That's a specific example.

I use https://github.com/39aldo39/klfc in my scripts to generate the OS-specific files for ANSI layouts. I convert the KLA json to their format. There may be bugs in that process. Checking it is on to-do list.

On Windows I am using DreymaR's extend layer to navigate in Vim using the directional keys on JKLI (qwerty). On Linux I used KLFC to create a custom keyboard replicating that of Dreymar's, I just tweaked a few keys on the examples folder to better suit my needs.

The OTHER Big News is that I now have install files for basic ANSI layouts. They are in Alpha/Beta state, I have not tested them and will welcome feedback. They are generated via the Keyboard Layout Files Creator @ https://github.com/39aldo39/klfc

The diaeresis appears on the bépo layout by default. It also has Greek letters, like say Σ. I have extended bépo by setting Caps Lock to work as a modifier key, so I get twice as much space. Every time I meet a new symbol I want to have, I put it somewhere on the keyboard. klfc is a fantastic tool for this.

How did you create your custom layout? I already found out about klfc, but 1. It doesn't work on wayland, 2. It's not entirely clear to me how to use this tool.

KLE .json has a lot of issues. Den and I have started talking about what we need. Probably needs a wider group. There is already this project as well as Kalamine