starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[PR #1399] Apply state socketmessage #1382

New Issue
Open
opened 2026-01-05 14:55:05 +01:00 by adam · 0 comments
adam commented 2026-01-05 14:55:05 +01:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/LGUG2Z/komorebi/pull/1399
Author: @pro470
Created: 4/4/2025
Status: 🔄 Open

Base: master ← Head: apply-state-socketmessage

📝 Commits (3)

  • 3fb4460 fix(wm): ensure workspaces count when apply the state
  • 20aed58 feat(wm): make the monitor workspaces the exact same length as the state Monitor workspaces
  • 5e2cddc feat(wm): opening the apply state function as a socketmessage for the first lower level command

📊 Changes

5 files changed (+18 additions, -6 deletions)

View changed files

📝 komorebi-bar/src/bar.rs (+1 -1)
📝 komorebi-bar/src/main.rs (+2 -2)
📝 komorebi/src/core/mod.rs (+3 -0)
📝 komorebi/src/process_command.rs (+3 -0)
📝 komorebi/src/window_manager.rs (+9 -3)

📄 Description

This is an attempt at a maybe low-level socket which could be helpful for a client connecting to komorebi.
It opens the ability to modify the data, but only needs one update, which means we only lock per display.
This is good for people wanting to configure komorebi with a scripting language. They can create a state and only send one state to komorebi for applying, which should be faster than using the socket message available right now.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/LGUG2Z/komorebi/pull/1399 **Author:** [@pro470](https://github.com/pro470) **Created:** 4/4/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `apply-state-socketmessage` --- ### 📝 Commits (3) - [`3fb4460`](https://github.com/LGUG2Z/komorebi/commit/3fb4460ac1593f9b6d8f30bb3be4a66b74110bdc) fix(wm): ensure workspaces count when apply the state - [`20aed58`](https://github.com/LGUG2Z/komorebi/commit/20aed5800639db6497fbad99e7737108d901c4f5) feat(wm): make the monitor workspaces the exact same length as the state Monitor workspaces - [`5e2cddc`](https://github.com/LGUG2Z/komorebi/commit/5e2cddcdec6e78012b672a6b8b04e8c160d5c3fd) feat(wm): opening the apply state function as a socketmessage for the first lower level command ### 📊 Changes **5 files changed** (+18 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `komorebi-bar/src/bar.rs` (+1 -1) 📝 `komorebi-bar/src/main.rs` (+2 -2) 📝 `komorebi/src/core/mod.rs` (+3 -0) 📝 `komorebi/src/process_command.rs` (+3 -0) 📝 `komorebi/src/window_manager.rs` (+9 -3) </details> ### 📄 Description This is an attempt at a maybe low-level socket which could be helpful for a client connecting to komorebi. It opens the ability to modify the data, but only needs one update, which means we only lock per display. This is good for people wanting to configure komorebi with a scripting language. They can create a state and only send one state to komorebi for applying, which should be faster than using the socket message available right now. <!-- Please follow the Conventional Commits specification. If you need to update your PR with changes from `master`, please run `git rebase master`. By opening this PR, you confirm that you have read and understood this project's `CONTRIBUTING.md`. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2026-01-05 14:55:05 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#1382
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?