Repository navigation
Conversation
A headless output is one more output of the remote's Hyprland session, and the session lock covers all of them. Say so in the README, next to the description of the private screen (omacom#136). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UCs6nfZCNssaXtUYR7cpHg
[Low impact] This documentation-only change appears safe to merge. SummaryAdds a warning after the private-screen description in
No actionable issues found. Unayung explicitly deferred keeping physical outputs blanked and locked, blocking local input, and adding a client warning. These need separate work. Reviews (1) · Last reviewed commit: "Warn that unlocking a private screen unl..." · Reviewed by Greptile |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #136.
Problem
The README calls
--headless"a private remote screen". The headless output is one more output of the remote's Hyprland session, and the session lock covers every output. Unlocking through gliff therefore also unlocks the remote's physical monitors, and someone at the remote machine can see and use the desktop. Nothing in the docs says so.Fix
Add a paragraph after the private-screen description. It says the private screen shares the remote's session and that unlocking through gliff unlocks the remote's own monitors too. It also says connecting can turn those monitors back on. This is the third option in #136.
Not in this PR
Testing
Docs only. The paragraph goes after a blank line that follows the paragraph #144 edits, so the two PRs merge cleanly (checked with
git merge-tree). The behaviour it describes is the one the reporter found withhyprctl -j monitors. I did not reproduce it on two machines.🤖 Generated with Claude Code
https://claude.ai/code/session_01UCs6nfZCNssaXtUYR7cpHg