docs: point the known-gaps list at the TODO folder, and un-stale its first item
Item 1 said the broker reads none of the container or pointer configuration. That was true and is not: the settings are parsed beside Policy and a switched-off container host reports itself unavailable with the key named. The item now records what actually matters about it -- that containers are off on the deployment machine because no window can be put in one -- and the section links docs/TODO/, where each open problem has its impact written down. The TODO folder itself landed in the previous commit by accident (a `git add -A docs` swept it in with the scroll work); this commit only makes it findable.
This commit is contained in:
1 parent
6b395305e0
commit
7e0544ed70
2 files changed
+18
-13
No files matched your search
@@ -21,6 +21,12 @@ machine cannot be mistaken for one whose compositor is down.
|
||||
|
||||
## Ideas
|
||||
|
||||
0. **This is already recorded from the other side**, in `README.dev.md` item 4:
|
||||
a window rule only binds for an application that reads the environment, and
|
||||
the fix proposed there is a per-app `--app-id` in the allowlist — a policy
|
||||
change. Idea 1 below sidesteps the question instead of answering it, because
|
||||
it needs nothing from the application at all.
|
||||
|
||||
1. **Adopt windows by the pid the compositor already reports.** *(recommended)*
|
||||
`hyprctl clients -j` gives each client's pid, and the broker already knows each
|
||||
session's pid — so the join is a lookup, and **no app has to take part**. No
|
||||
|
||||
Reference in new issue
Block a user