From: Jstsmthrgk <jstsmthrgk@jstsmthrgk.eu>
To: 9front@9front.org
Subject: aux/kbdfs: changes to allow support of NEO2 layout
Date: Sat, 18 Apr 2020 23:13:14 +0200 [thread overview]
Message-ID: <7bc5ada8-ba76-bca2-ad96-19cedf8ae5fa@jstsmthrgk.eu> (raw)
I would really like to add support for NEO2 layout [0], but I've got two
problems:
First of all, the NEO2 layout uses six layers, while the current kbdfs
only allows for four of them (out of the eight tables three are only
used to allow multi-byte keycodes starting with E0 and another one is
used for something with the ctrl key). Therefore I would have to add two
more tables to kbdfs (and one more Private Unicode Space Rune to
keyboard.h). As this would be my first ever contribution to 9front I
wanted to ask beforehand if there is anything I have to pay attention to?
The second one is that there are many dead-keys in the NEO2 layout, it
seems like currently those are replaced by the compose key in the
current implementation. I guess I should just do it alike?
I would really value some feedback beforehand, as already stated, this
would be my first ever contribution. (I will try to program it tomorrow)
[0] https://neo-layout.org/
next reply other threads:[~2020-04-18 21:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 21:13 Jstsmthrgk [this message]
2020-04-19 17:35 ` [9front] " sirjofri
2020-04-19 20:16 ` Jstsmthrgk
2020-04-19 20:37 ` Sigrid Zirukin
2020-04-19 21:02 ` Jstsmthrgk
2020-04-20 12:52 ` Jstsmthrgk
2020-04-20 13:03 ` Sigrid Solveig Haflínudóttir
2020-04-21 14:44 ` ori
2020-04-21 18:21 ` Jstsmthrgk
2020-04-24 21:22 ` jstsmthrgk
2020-04-25 19:55 ` ori
2020-04-26 3:47 ` ori
2020-04-26 9:16 ` Jstsmthrgk
2020-04-26 9:18 ` qwx
2020-04-26 9:30 ` Jstsmthrgk
2020-04-26 9:35 ` qwx
2020-04-26 16:08 ` ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7bc5ada8-ba76-bca2-ad96-19cedf8ae5fa@jstsmthrgk.eu \
--to=jstsmthrgk@jstsmthrgk.eu \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).