Mariano Abad
f436f53f0d
Review of the first version, all three correct. The important one: `connect_to_env()` honours `WAYLAND_DISPLAY` and `WAYLAND_SOCKET`, and the fallback ignored that choice. If an explicit endpoint was named and failed, this could attach to a *different* compositor and read output positions from the wrong display. It now runs only when neither variable is set, which is also the only case it was ever justified by. `XDG_RUNTIME_DIR` is read with `var_os` and rejected when relative, since `.` or `../tmp` would probe against the working directory. And every failed probe is kept instead of the last one overwriting the first, so an error naming both sockets says what happened to both. The comment is three lines now: the reasoning belongs here, in the commit.