Conversation
Super+J sent layoutmsg togglesplit unconditionally, which Hyprland rejects on a scrolling workspace. Dispatch consume_or_expel on scrolling instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Super + Jalways dispatched dwindle'stogglesplit. On a scrolling workspace Hyprland raisesno such layoutmsg for scrollingand shows a Lua runtime error overlay.The bind now checks the active (or special) workspace layout:
togglesplit(unchanged)consume_or_expel next(stack a lone column into its neighbor, or expel a stacked window)Testing
bash test/shell.d/hyprland-window-split-toggle-test.sh: passedbash test/shell.d/hyprland-binding-conflicts-test.sh: passed./test/cli: passedhyprctl configerrorsclean after reload; dispatching the new path on a one-window scrolling workspace no longer raises the Lua runtime error