✨ Independent stash per space
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
No files, tests, or entry points are named. Start by tracing how stash state is stored and updated when switching spaces, then determine where space identity is available to that state. Done means Chrome remains stashed in Space 01 and Edge remains independently stashed in Space 02 after moving between spaces.
Written by the indexing model from the issue text.
Description
Feature Request Summary
I hope I'm not repeating any existing feature requests here (I've looked around using "stash" as keyword). I think the stash feature should be handled independently in each space.
Problem / Opportunity & Desired Solution
Current behavior:
- Space 01 has Chrome stashed to right side
- Move to Space 02, set Edge to be stashed to the right side
- Move back to Space 01, now Chrome is out of its stashed position and will not be stashed anymore
Desired behavior:
- Space 01 has Chrome stashed to right side
- Move to Space 02, set Edge to be stashed to the right side
- Move back to Space 01, Chrome should be still stashed and can be interacted as normally. So does Edge when user is move to Space 02
Alternatives Considered
No response
Visuals or References
No response
Additional Context
This request probably can be extended if there is multiple display being connected. But, I can't have any say to that because currently not in a multi-display setup
Priority
Medium (important but not blocking)
Final Checks
- My issue is written in English.
- My issue title is descriptive.
- This is a single feature request (multiple feature requests should be reported individually).
- I have looked to see if this is a duplicate of another feature request.
- I can help with research or testing.
- I can help code this feature.
- Dominant language
- Swift
- Stars
- 11.9k
- Forks
- 287
- Avg merge
- 17h 7m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mrkai77/Loop
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
🐞 Crash when editing the search field in the keybind action pickerPossibly taken @NicoCorini claimed this 10 days ago. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
mrkai77/Loop#1187 · 4 comments ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
mrkai77/Loop#1191 · 1 reaction ·
Maintainers usually reply within 1 day
-
✨ Prioritize Custom Trackpad Gestures Over Default Radial Menu GesturesPossibly taken @mrkai77 claimed this 16 days ago. OpenFeature
Difficulty 4/5 3-5 days Newbie friendliness 25/100
mrkai77/Loop#1177 · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
swiftlang/swift-markdown#299 ·
-
area: agents follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
manaflow-ai/cmux#37234 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
bug product / functions
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
JWhite212/SignalLadder#215 ·
Maintainers usually reply within 1 day