9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] aux/kbdfs: changes to allow support of NEO2 layout
Date: Sun, 19 Apr 2020 19:35:43 +0200	[thread overview]
Message-ID: <CAF5U_z1gqz1gp9zQ1Sgcv=KsrVqc9dRLMXn1vSG7pq9AtSremg@mail.gmail.com> (raw)
In-Reply-To: <7bc5ada8-ba76-bca2-ad96-19cedf8ae5fa@jstsmthrgk.eu>

Hello,

Jstsmthrgk <jstsmthrgk@jstsmthrgk.eu> schrieb am Sa., 18. Apr. 2020, 23:15:
> I would really like to add support for NEO2 layout [0], but I've got two
> problems:

Fun fact: yesterday I also thought about adding neo2 support to
9front. More like a coding challenge and to learn programming for 9.

> First of all, the NEO2 layout uses six layers, while the current kbdfs
> only allows for four of them

Some of these tables use other layers, but I don't know how to
activate them and if they are used simultaneously. I also didn't look
into kbdfs, I only looked at the tables. I remember the po keymap file
using some layer 7 or so? Also I don't know if you can activate layers
with a combination of modifier keys (like neo wants).

> 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?

I wish you every luck and also a lot of fun. I never contributed code
to any open source project, but I want to help if I can.

Please let me know if I can help somehow. I am a native German speaker
and can help testing and maybe review/write some code. I am not that
experienced with the native plan9 C libraries (and also no
professional with the libc). I'm also not that experienced with neo2,
but I am very interested and also learned it a little.

I only have one real limitation: My current native plan9 terminal is a
thinkpad T61 which has a limited keyboard. Also it's imported and had
a very weird keyboard layout (with stickers on the keycaps). I already
missed the <>| keynext to the left shift key on the German layout, so
I use the us layout.

I hope I can still help you somehow and make 9 a better place.

sirjofri

(This is a duplicate mail, I tried sending it from the gmail app.
Gmail app does not support sending plain text messages, so it's
possible that this mail is doubled. This is the plain text version.)


  reply	other threads:[~2020-04-19 17:35 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-18 21:13 Jstsmthrgk
2020-04-19 17:35 ` sirjofri [this message]
2020-04-19 20:16   ` [9front] " 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='CAF5U_z1gqz1gp9zQ1Sgcv=KsrVqc9dRLMXn1vSG7pq9AtSremg@mail.gmail.com' \
    --to=sirjofri@sirjofri.de \
    --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).