Home Apple Keyboard – Put in Karabiner, now getting ⧠as a substitute for ~

Keyboard – Put in Karabiner, now getting ⧠as a substitute for ~

0
Keyboard – Put in Karabiner, now getting ⧠as a substitute for ~

Glad New Yr everybody!

Apple MacBook Pro 14-inch M3: Professional-grade performance with latest software updates applied. US English format.

Here is the rewritten text:

I aimed to remap LOpt + i/j/k/l to arrow keys, enabling me to stay on the home row and avoid shifting my right hand to navigate. I’ll ensure that the built-in keyboard is configured correctly for your external QWERTY keyboard, specifically designed for the QK100 model.

After installing Karabiner-Components via brew,

Despite my best efforts to set up Karabiner correctly, I’ve inadvertently mapped my external keyboard’s tilde/backtick key to produce §/± symbols instead, despite having configured the System Settings for US English/ANSI layout, as far as I can tell. The inner keyboard’s functionality operates seamlessly, yielding a precise output of forward slashes and tilde symbols. Despite uninstalling Karabiner, which seemed to coincide with the problem’s onset, I still find myself stuck on the §/± conundrum.

Can someone help me revive my external keyboard’s tilde key, allowing me to explore ways to remap the i j k l keys as alternative arrow keys for smoother navigation?

I’ve struggled with Karabiner’s finicky behavior before – I’ve reloaded the profile, restarted my Mac, and still nothing works as expected? I nonetheless get §/±.

I’ve also noted that the keyboard’s behavior is exclusive to Mac mode. Despite configuring the keyboard’s software correctly to map the apostrophe to the grave accent or tilde, reverting back to “Windows” mode solves the problem altogether. Unfortunately, this setting simultaneously disables me from utilizing the correct modifier keys, thereby rendering my preference for preserving Mac mode moot. I have contacted the manufacturer to determine whether they can provide assistance, but since the problem only occurs on Mac OS, I am uncertain as to whether the issue lies with their end.

To circumvent this issue, I employ a temporary solution that involves using QK100 to remap the ~ key to NUBS, followed by configuring Karabiner to map NUBS to the grave accent (~). The conventional restoration was successful, but identifying the root cause of the problem would provide more insight and facilitate targeted improvements?

LEAVE A REPLY

Please enter your comment!
Please enter your name here