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 #860] [CLOSED] Updated documentation to make binding a display to a given index clearer #1123

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

📋 Pull Request Information

Original PR: https://github.com/LGUG2Z/komorebi/pull/860
Author: @NireBryce
Created: 6/1/2024
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (1)

  • 4e26fc3 Updated documentation to make it clearer how to bind a display to a given index

📊 Changes

3 files changed (+23 additions, -1 deletions)

View changed files

➕ docs/common-workflows/set-display-index.md (+15 -0)
📝 mkdocs.yml (+1 -0)
📝 schema.json (+7 -1)

📄 Description

Hey, I had a hard time figuring out how to do this with what was posted in the github issues + documentation, so I wrote what I found.

I couldn't really discern style from the other workflow examples, but hopefully the common-workflow doesn't need much extra work to bring it to that.

(special thanks to javierportillo, who I do not know but found a usable config line via github codesearch)

🔄 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/860 **Author:** [@NireBryce](https://github.com/NireBryce) **Created:** 6/1/2024 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (1) - [`4e26fc3`](https://github.com/LGUG2Z/komorebi/commit/4e26fc324ed19f789793c5eb45af0ace55ca2f84) Updated documentation to make it clearer how to bind a display to a given index ### 📊 Changes **3 files changed** (+23 additions, -1 deletions) <details> <summary>View changed files</summary> ➕ `docs/common-workflows/set-display-index.md` (+15 -0) 📝 `mkdocs.yml` (+1 -0) 📝 `schema.json` (+7 -1) </details> ### 📄 Description Hey, I had a hard time figuring out how to do this with what was posted in the github issues + documentation, so I wrote what I found. I couldn't really discern style from the other workflow examples, but hopefully the common-workflow doesn't need much extra work to bring it to that. (special thanks to javierportillo, who I do not know but [found a usable config line](https://github.com/javierportillo/.dotfiles/blob/227e1bdc5bd9cd262685e2d5a676e050f66beb8e/home/.config/komorebi/komorebi.json#L14) via github codesearch) --- <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:54:11 +01:00
adam closed this issue 2026-01-05 14:54:11 +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#1123
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?