Ich nutze OSX Sierra.
Manchmal sind die Tastendrücke verzögert, es kommen für einige Sekunden (mal länger, mal kürzer) keine Tastendrücke an, auch z.B. Karabiner Eventviewer zeigt dann nichts an. Nach Ablauf dieser Zeit kommen dann aber alle Tastendrücke auf einmal.

Es betrifft sowohl die interne als auch eine externe Tastatur. Das Problem tritt während des Betriebs zufällig auf und vermehrt nachdem der Laptop im Standby war (aber nicht immer).
Ohne Karabiner Elements Neo scheint das Problem nicht aufzutreten.
Vermutlich das gleiche wie hier: pqrs-org#502

Allerdings ist der Post schon etwas älter, ggf. löst die aktuelle Karabiner Elements Version das Problem auch schon. Ist geplant Karabiner Elements Neo auf die aktuelle Version zu updaten?

For be the layer 4 + ü wites the big ẞ instead of the minus sign.

This happens for both modifier keys, >/< (M4) and right cmd (Mod4). All other keys of layer 4 seem to work as expected.
Do you need any logs?

I use an ergodox keyboard. I have a certain key setup to emit the "<" key, the same key that is used for mod4 on the internal keyboard (i.e. when Karabiner Elements is quit, both the mod4 keys print "<" in a text editor).
However, when I launch Karabiner Elements (Neo), layer 4 works on the internal keyboard, but on the ergodox the mod4 key just emits "^" (i.e. layer 4 does not work).

Any ideas on how to fix this?

Hi, ich weiß nicht ob ich was falsch gemacht habe, aber nachdem ich den MAKE Befehl ausführe kommt folgende Meldung

..............................................................** BUILD FAILED **

The following build commands failed:
CompileC build/libkrbn.build/Release/libkrbn.build/Objects-normal/x86_64/libkrbn_system_preferences_monitor.o libkrbn_system_preferences_monitor.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)
make[4]: *** [all] Error 65
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [build] Error 2

make: *** [all] Error 99

Ich hoffe du hast eine Ahnung was das ist.
LG Husky

Occasionally, I would like to switch to German / US layouts. Then, it would be convenient to have the Neo mappings disabled. (IIRC, with the original Karabiner, there were profiles that could be used for this, but maybe that was not the best interface anyhow.) What do you think? Shall we open an upstream issue? (I guess that the whole -Neo variant should eventually be upstreamed?)

Is that Feature possible?

Holding the left option key also activates layer 3 (and 5/6 when combined with other modifiers).
I am relatively new to Neo, so I may be wrong about the intended behavior, however since the diagrams on the Neo homepage do not highlight the Left Alt key, I did not expect this to be the case.

Furthermore Mod3 still causes the option key to be recognized by applications, which I also did not expect.
This triggers unintended shortcuts in many applications and I see no way around it except unbinding all shortcuts including Option, making it entirely unusable.

I hope there are ways to change this behavior and thank you in advance for looking into it.

Mod3+- (Neo) / Mod3+ß (Qwertz labels) doesn’t do anything; it should produce an em dash: —

I tried adding it myself but did not succeed. Maybe I can help more if you tell me:

• How do I find out the krbn::key_code number of a key? They don’t seem related to these Karabiner hex key codes.
• I see the Layer 4 mappings in src/core/grabber/include/manipulator/event_manipulator.hpp, but where are Layer 3 mappings? Are they entirely in neo.keylayout and if so, why is this particular symbol missing?

From this comment:

CapsLock/Right Cmd + qwerty-asdf are the cursor keys. But adding shift to select text does not work, but did before.

I should check whether other keys in layer 4 might be useful with the shift modifier.

When pressing said combinations in neo the qwerty-equivalent is sent. This makes it impossible to assign actions to these keys in editors / IDEs / whatever.

First, this is merely a suggestion, since it’s beyond the scope of implementing Neo, so feel free to close. But I find it extremely useful, and perhaps you do too:

With Karabiner it was possible to remap Tab ⇥ to Control ⌃ (or some other modifier), but only if combined with other keys. In other words, simply pressing and releasing the key alone would still produce a tab. Also, Capslock ⇪ + Tab ⇥ would still trigger Compose ♫.

I found this to be a huge ergonomic improvement, and I miss it dearly.

Is this sort of remapping possible using the current code?

Note to self: alols/xcape does this for Linux: “modifier keys act as other keys when pressed and released on their own”.

In Karabiner, you can map the "Application" key many windows keyboards have. I use a Microsoft Sculpt Ergonomic Desktop which has this particular key and would like to map it to right option, but I can't find it in the source key drop down menu.

The same goes for the "<" and "^"-keys as MacOS is swapping them on my keyboard for whatsoever reason.

Is this not implemented or am I missing something?

• README.md
• Wiki page with build instructions

Occasionally my (left) Cmd key “sticks”, i.e., behaves as though it is pressed even though it is not. Pressing it again “releases” it.

I haven’t noticed a pattern regarding what exactly triggers it, in fact I’m not sure that this is due to Karabiner Elements Neo. But I never had the issue when using Karabiner, so it seems a likely suspect.

Mainly I’m posting to see if anyone else has noticed this, to confirm my suspicions.

I was told by the neo irc, that it should be possible to produce "ñ" as e.g. used in spanish using Compose:
♫+~+n or
♫+n+~

Unfortunately, this does not work atm. Is it possible to fix this?

Mod3 + "o" (Neo) doesn't insert "*" in text-fields on some web-pages but takes one a page back in history.

When I map the keys as described in the manual, each press of M3 (no matter if left or right) makes the "pop the window back and show the menu bar" effect. If I release it and press again before the zoom out effect fades, I can use Layer 3, but that's no long term solution.

Keyboard: internal, MacBook Air Early 2015
MacOS Sierra 10.12.5 (16F73)

Any knowledge about that out there?

I'm used by the old layout to have right-option mapped to cmd.
Don't know if this is the default, but I think it is part of the official setup tutorial.
Maybe just add right_option to left_command in the README :)

Hi, ich wollte gerade Neo2 auf meinem zweit Mac installieren und bekomme beim Ausführen von make folgende Fehlermeldung:

git clean -f -x -d
Removing pkginfo/Distribution.xml
Removing src/apps/EventViewer/Info.plist
Removing src/apps/PreferencesWindow/PreferencesWindow/Info.plist
Removing src/apps/Updater/Updater/Info.plist
Removing src/share/karabiner_version.h
Removing src/vendor/Karabiner-VirtualHIDDevice/src/Info.plist
./make-package.sh
make build
......xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
make[4]: *** [all] Error 1
make[3]: *** [all] Error 2
make[2]: *** [all] Error 2
make[1]: *** [build] Error 2

make: *** [all] Error 99

Vielen Dank schonmal für die Antwort,
Liebe Grüße Husky

First of all, thanks for finally being able to use layer 4 on my MBA/Sierra again. However, I'd like to report / discuss that this does not work with external keyboards. I like to keep my MBA closed, with two setups in two different offices:

1. Power adapter + thunderbolt, with ethernet, graphics, and USB hub via the monitor / thunderbolt cable. Mouse, keyboard etc. connected via that USB hub.
2. Power adapter + displayport graphics + USB KVM switch. (Although the same type of Microsoft keyboard is connected, its USB identifier is "hidden" by the KVM switch.)
   In both settings, I am getting a "dead ^" with the mod4-key (leading to ĥ instead of 7, ^m instead of 1, ⁿ instead of 4).

I'd like to know whether it's a well-known limitation, a bug, or a misconfiguration on my side.

From this and this comment:

After trying it for a few minutes, the only odd thing I notice is Home/Pos 1 & End (i.e., Mod4+U/O (Neo) = Mod4+A/G (Qwertz labels)). In my El Capitan / Karabiner setup, they move the cursor to the beginning/end of line (when in a text field), while now they scroll to the top/bottom. (Maybe that’s actually intended, but I’m definitely not used to it.)

CapsLock/Right Cmd + Qwerty-A used to jump to the beginning of the line, but now instead scrolls up.

I think those keys are supposed to map to the Home and End keys in the Neo layout (verify this). It seems that the macOS behaviour for these keys is supposed to be what it is right now (unfortunately I do not have a keyboard with actual Home and Endkeys to test). But it seems that people (and me) prefer to have those keys mapped as what probably isCmd+LeftandCmd+Right`.

What is more important?

• Stay true to the actual Neo2 layout?
• Keep the behaviour from previous Neo2 implementations on the Mac?
• Use the behaviour most people prefer?

I suppose ideally this could be configured, but this would be a more complex change and I would need to understand more of the code base to do it.

Hello,

I installed the Karabiner-Elements as described here. Luckily, I can use all 6 layers.

Unfortunately, neo only works in certain programs (Safari, Chrome, Finder, …) but not in others (Pages, TexStudio, Mail, …). Not working means that I cannot choose the neo-Keyboard as Input Source although it is displayed.

However, I can use the arrow keys and the number pad of Layer 4 whenever I am in the standard German / English keyboard. The rest of Layer 4 works in neo,  provided neo is working.

I guess it cannot overwrite the application specific keybindings.

Thanks in advance!

Linda