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

[FEAT]: Scratchpad #620

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

Originally created by @rlopeznegrete on GitHub (May 15, 2025).

Eligibility

Individual Commercial Use License

Suggestion

This idea has been discussed in Discord and in the discussions section. I wanted to be able to get updates if there's any change in this topic. I searched in the other issues, but did not find the scratch pad mentioned. So I hope this issue helps to keep me and others informed.

Feel free to close if this is redundant! Thanks!

Alternatives Considered

for now I keep a floating layer open in multiple workspaces and keep multiple widows of the same application opened in them (or keep moving the same application between workspaces).

Originally created by @rlopeznegrete on GitHub (May 15, 2025). ### Eligibility Individual Commercial Use License ### Suggestion This idea has been discussed in Discord and in the discussions section. I wanted to be able to get updates if there's any change in this topic. I searched in the other issues, but did not find the scratch pad mentioned. So I hope this issue helps to keep me and others informed. Feel free to close if this is redundant! Thanks! ### Alternatives Considered for now I keep a floating layer open in multiple workspaces and keep multiple widows of the same application opened in them (or keep moving the same application between workspaces).
adam added the enhancement label 2026-01-05 14:52:00 +01:00
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 15, 2025):

Feature requests on this repository are only open to current GitHub sponsors on the $5/month tier and above, people with a valid individual commercial use license, and approved contributors.
This issue has been automatically closed until one of those pre-requisites can be validated.

@github-actions[bot] commented on GitHub (May 15, 2025): Feature requests on this repository are only open to current [GitHub sponsors](https://github.com/sponsors/LGUG2Z) on the $5/month tier and above, people with a valid [individual commercial use license](https://lgug2z.com/software/komorebi), and approved contributors. This issue has been automatically closed until one of those pre-requisites can be validated.
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (May 18, 2025):

I'm personally pretty happy with the floating layer for this kind of workflow right now, but I'm open to mentoring someone who would like to try working on this

@LGUG2Z commented on GitHub (May 18, 2025): I'm personally pretty happy with the floating layer for this kind of workflow right now, but I'm open to mentoring someone who would like to try working on this
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@rlopeznegrete commented on GitHub (May 20, 2025):

I'm personally pretty happy with the floating layer for this kind of workflow right now, but I'm open to mentoring someone who would like to try working on this

I understand, I'm unfortunately not savvy enough in Rust to implement something like this.

However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces.

What do you think about someting like that?

@rlopeznegrete commented on GitHub (May 20, 2025): > I'm personally pretty happy with the floating layer for this kind of workflow right now, but I'm open to mentoring someone who would like to try working on this I understand, I'm unfortunately not savvy enough in Rust to implement something like this. However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces. What do you think about someting like that?
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (May 20, 2025):

However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces.

This is basically the entire scratchpad implementation 😅 The biggest part of the work is understanding how to divorce window state from workspaces, possibly to the monitor level, maybe even to the window manager level

@LGUG2Z commented on GitHub (May 20, 2025): > However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces. This is basically the entire scratchpad implementation 😅 The biggest part of the work is understanding how to divorce window state from workspaces, possibly to the monitor level, maybe even to the window manager level
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@rlopeznegrete commented on GitHub (May 20, 2025):

However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces.

This is basically the entire scratchpad implementation 😅 The biggest part of the work is understanding how to divorce window state from workspaces, possibly to the monitor level, maybe even to the window manager level

this goes to show how little I understand this codebase. If it's all the same to you let's keep the issue open for sometime in case there's any takers.

thanks!

@rlopeznegrete commented on GitHub (May 20, 2025): > > However, as a kind of compromise, is it easier to implement an option to make the floating layer common to all workspaces? This way some can have floating layers for each workspace, or a single floating layer (as a scratchpad) that is the same for all workspaces. > > This is basically the entire scratchpad implementation 😅 The biggest part of the work is understanding how to divorce window state from workspaces, possibly to the monitor level, maybe even to the window manager level this goes to show how little I understand this codebase. If it's all the same to you let's keep the issue open for sometime in case there's any takers. thanks!
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@ECon65 commented on GitHub (May 23, 2025):

floating layer is on a good way to become a scratchpad like replacement. Have you considered extending its functionality using following options?

  1. Introduce two settings
  • one that enables floating layer to be shared across all workspaces on the same monitor
  • second that hides all windows in the floating layer by default
  1. Introduce two commands
  • one to cycle through windows in the floating layer. Something similar like cycling through the stack. In this case cycle would unhide first window from floating layer, if repeated it will hide the existing window and unhide the next one (like Alt+Tab but hiding the window you switch from)
  • second to toggle hide/unhide all windows in floating layer. When hide is enabled by default this command helps sometimes to check what is running in the floating layer.

That is just an idea how to create scratchpad (floating layer) for each monitor where you can place windows and call for them whenever you need them on whatever workspace you are currently on.

@ECon65 commented on GitHub (May 23, 2025): floating layer is on a good way to become a scratchpad like replacement. Have you considered extending its functionality using following options? 1. Introduce two settings - one that enables floating layer to be shared across all workspaces on the same monitor - second that hides all windows in the floating layer by default 2. Introduce two commands - one to cycle through windows in the floating layer. Something similar like cycling through the stack. In this case cycle would unhide first window from floating layer, if repeated it will hide the existing window and unhide the next one (like Alt+Tab but hiding the window you switch from) - second to toggle hide/unhide all windows in floating layer. When hide is enabled by default this command helps sometimes to check what is running in the floating layer. That is just an idea how to create scratchpad (floating layer) for each monitor where you can place windows and call for them whenever you need them on whatever workspace you are currently on.
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@rp1231 commented on GitHub (May 31, 2025):

Yep, a global scratchpad which can be shared across workspaces would be nice!

@rp1231 commented on GitHub (May 31, 2025): Yep, a global scratchpad which can be shared across workspaces would be nice!
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@adam-fff commented on GitHub (Sep 11, 2025):

I would find this v useful

@adam-fff commented on GitHub (Sep 11, 2025): I would find this v useful
adam commented 2026-01-05 14:52:01 +01:00
Author
Owner
Copy Link

@repolling commented on GitHub (Nov 15, 2025):

this would be very helpful

@repolling commented on GitHub (Nov 15, 2025): this would be very helpful
adam commented 2026-01-05 14:52:02 +01:00
Author
Owner
Copy Link

@KarthikKaravatt commented on GitHub (Dec 2, 2025):

i would cry tear of joy if this was added

@KarthikKaravatt commented on GitHub (Dec 2, 2025): i would cry tear of joy if this was added
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 enhancement
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#620
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?