You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hyprland does an odd thing in its usage of hyprlang with submap = ..., which switches into different submaps when binding keys (ideally this would've been implemented as different submap:xyz { ... } sections, but they Decided To Do It That Way for some reason)
because this specific section of keybinds needs to be surrounded by submap boundaries, it's not possible to do this with wayland.windowManagers.hyprland.settings
solution
the proposal is to add wayland.windowManagers.hyprland.submaps, like so:
hyprland
does an odd thing in its usage ofhyprlang
withsubmap = ...
, which switches into different submaps when binding keys (ideally this would've been implemented as differentsubmap:xyz { ... }
sections, but they Decided To Do It That Way for some reason)because this specific section of keybinds needs to be surrounded by
submap
boundaries, it's not possible to do this withwayland.windowManagers.hyprland.settings
solution
the proposal is to add
wayland.windowManagers.hyprland.submaps
, like so:workaround
wayland.windowManagers.hyprland.extraConfig
exists, but having part of the config in a string and the rest in nix options is frustratingThe text was updated successfully, but these errors were encountered: