NormalNvim VS zmk

NormalNvim is a middle ground between both.

This fix is included in NormalNvim, you can check the fix here. By mapping TAB this way, pressing TAB won't trigger the behavior of .

The mapping `gd` works correctly as described in the wiki. If you cannot use it, it means you have to use mason to install LSP support for go with `pm`

features

I still haven't released it officially, but in the meantime * You can find it here. * You can find the mappings here.

The mappings file of the nvim distro I'm about to release: NormalNvim

It's creative commons? I'd love to use It for my nvim distro NormalNvim

I definitely think you should be able to add keyboard layouts at a software level on iPadOS and iOS, but one possible solution to the problem right now is using a programmable keyboard using QMK [1], ZMK [2], or some other open-source firmware. There's even a usb-usb converter [3] that will convert keystrokes from any keyboard into ones that you map using TMK or QMK, so you can use your own.

[1] https://qmk.fm/

[2] https://zmk.dev/

[3] https://geekhack.org/index.php?topic=69169.0

I saw this same question was posted half a year ago and was wondering if anyone knew of any updates. Looks like this development branch of ZMK is stalled.

Not sure which information you mean, but here goes. Nice!Nano v2 Pinout (shows Arduino pin mapping). Nice!View Getting Started (explains how to remap the CS pin for a non-native shield like Corne). The overlay file where "cs-gpios" is set for the nice_view_adapter in ZMK. If you look at the Corne Schematic, you'll see as shown in the labels in this image that the bottom two pins (B2, B4, B5, B6) don't appear to be used for a column, row, or the OLED header. But the only way to really verify is to pull the KiCAD file for your Corne version and check yourself. I think D0 ("Data") should work. It appears to go to an optional I2C connection.

if you built the firmware using the corne shield that might be the issue. the splitkb aurora corne has a different pinout.

Depending on a controller you will be programming features of your keyboard using QMK or ZMK (there are alternatives but these two are the most popular). You can check documentation of these tools regarding display but some nice sum up is in the related article on splitkb: https://docs.splitkb.com/hc/en-us/articles/360010533820-What-can-you-use-an-OLED-display-for-

corne-ish zen, the group buy is long over but there is an extras round coming up. I suggest going on the discord if you're interested in knowing when they'll be available for sale. it is a prebuilt so you can just buy it whole and have it ready to use out of the box and runs on ZMK.

I would be pretty interested in a wireless Ploopy. Especially if it runs ZMK since that is what I currently use for a split keyboard. It would be pretty awesome to link the macros and layers between my keyboard and mouse if the mouse could be a second peripheral "half" of the keyboard. Admittedly, ZMK's mouse support is still kinda beta, but the wireless support is amazing.

The other firmware I wrote for my wireless programable keyboard based on ZMK.