randr: quit when no screens found & not active #801
Merged
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.
fvwm would quit when there were no screens detected by RandR. However,
this can be problematic with laptop screens which can be turned off.
If fvwm receives an RandR event to rescan screens, that can therefore
cause RandR to tell us there's no screens found. This is not true
though since the number of configured screens from fvwm's perspective
is still the same.
In such cases then, fvwm should only quit when the number of configured
screens is 0 and RandR hasn't detected any screens either.
Problem reported by @farhaven (Gregor Best)