Skip to content

fix(brightness): pass target monitor to DPMS dispatch in omarchy-brightness-display - #9108

Open
harshithnadig wants to merge 1 commit into
omacom:quattrofrom
harshithnadig:fix/brightness-display-monitor-dpms
Open

fix(brightness): pass target monitor to DPMS dispatch in omarchy-brightness-display#9108
harshithnadig wants to merge 1 commit into
omacom:quattrofrom
harshithnadig:fix/brightness-display-monitor-dpms

Conversation

@harshithnadig

Copy link
Copy Markdown

Problem

In #9077, running omarchy brightness display --monitor <output> off blanks all connected monitors instead of only the specified display.

Cause

bin/omarchy-brightness-display parses and resolves $monitor, but the off and on branches dispatched global hl.dsp.dpms({ action = "disable" }) calls without passing the monitor parameter.

Solution

Pass monitor = "$monitor" into hl.dsp.dpms so that DPMS disable/enable calls target the requested monitor output, consistent with omarchy-hyprland-monitor-clamshell.

Fixes #9077

…htness-display

'omarchy-brightness-display' accepts '--monitor <name>' and defaults to the
focused monitor, but the 'off' and 'on' branches dispatched global DPMS
actions without specifying the monitor key, causing a single blanking
command to turn off all connected displays.

Pass 'monitor = "$monitor"' to 'hl.dsp.dpms' when targeting a specific
output for off/on actions.

Fixes omacom#9077
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

omarchy-brightness-display documents --monitor but off/on ignore it, so a single display cannot be blanked

1 participant