Return to Answer

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb. This article goes into detail on how Wayland and XWayland works with user-specific XKB configurations.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb. This article goes into detail on how Wayland and XWayland works with user-specific XKB configurations.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb. This article goes into detail on how Wayland and XWayland works with user-specific XKB configurations.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.

You should be using libxkbcommon instead of xmodmap by creating $HOME/.config/xkb. This article goes into detail on how Wayland and XWayland works with user-specific XKB configurations.

Wayland's keyboard configuration works like this:

• the compositor decides on the RMLVO keybard layout, through an out-of-band channel (e.g. gsettings, weston.ini, etc.)
• the compositor invokes libxkbcommon to generate a KcCGST keymap and passes that full keymap to the client
• the client compiles that keymap with libxkbcommon and feeds any key events into libxkbcommon's state tracker to get the right keysyms

The advantage we have here is that only the full keymap is passed between entities. Changing how that keymap is generated does not affect the client. This, coincidentally, is also how Xwayland gets the keymap passed to it and why Xwayland works with user-specific layouts.

I'm using Sway as well and haven't had any problems with my custom layout. This is my config with its own comprehensive README. There's additional resources in there as well.