[Keymap] Add brauner preonic layout

[brauner]

Signed-off-by: Christian Brauner brauner@kernel.org

Add a new keymap for the preonic keyboard.

Description

This is a keymap layout heavily optimized for vim.
It mostly follows QWERTY but moves various symbols on to different layers.

• Number keys function only as number keys.
  Additional symbols they would produce when Shift is held are turned off as they are intercepted.
• Y, P, and X function as Ctrl+C, Ctrl+V, and Ctrl+X when held.
  This avoids having to hold down Ctrl and also aligns regular copy and paste with vim functionality.
• Various keys perform different functions when tapped than when held.
• ! and ? are on top of . on different layers.
• \ and | are on top of / on different layers.
• : and ; are on top of , on different layers.
• All navigation is done via H, J, K, and L.
• O, U, S, and A produce the Umlauts Ö, Ü, ß, and Ä when held.
  This relies on the operating system keyboard layout to be set to US Intl.
• Different layers will activate different types of navigation.
  For example, left, right, up, and down or backspace, page up, page down, and tab.
• There's a dedicated mouse layer which can be activated allowing to navigate solely with the keyboard where otherwise a mouse or trackpad would be needed.
• There's a dedicated management layer where the boot loader can be entered or music mode can be turned on or off.
• Lastly, there's a compositor layer which is optimized for managing a tiling window manager.
  The layer is used specifically via layer-mod keys in the base layer.
  In other words, specific modifiers are held when this layer is accessed.
• Opening and closing brackets are always located on adjacent keys on the same layer.
  Pressing a matching opening and closing bracket key at the same time will insert both brackets and move the cursor into the middle of the bracket pair.
  As should be obvious, this is useful when programming: (|), [|], {|}, <|>.

Types of Changes

• Core
• Bugfix
• New feature
• Enhancement/optimization
• Keyboard (addition or update)
• Keymap/layout/userspace (addition or update)
• Documentation

Checklist

• My code follows the code style of this project: C, Python
• I have read the PR Checklist document and have made the appropriate changes.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have tested the changes and verified that they work and don't break anything (as well as I can manage).

[brauner]

So I've looked through git history and I'm a bit puzzled that so many new keymap additions have a Co-developed-by: tag attached to them. As a kernel maintainer and developer that tag is really only given when most of the contents of the patch are based on the joint work of multiple people.

In any case, happy to hear your thoughts. I've squashed all commits I had into a single one and tried to follow the example of the other keymap additions.

[drashna]

Mostly, just some clean up suggestions

[brauner]

Mostly, just some clean up suggestions

Thanks! I incorporated them and force-pushed a new version just now.

[brauner]

Seems that this is ready to merge? Let me know if there's anything else I need to do.

[drashna]

Thanks!

[brauner]

Thank you!