modes unassigned to outputs not shown distinctly
Submitted by chrysn
Assigned to Keith Packard @keithp
Description
in verbose mode, there is no way to tell modes that are not assigned to any output apart from modes that are assigned to the last output.
i suggest that if (res->nmode > 0)
around xrandr.c:3221 (line numbers as of git d58d70f6), a message like "Not assigned to any output:\n" should be printed.
(due to what i guess is a bug, it is currently possible to tell them apart under some circumstances -- the code blocks xrandr:3161-3184 and 3221:3237 are identical but for "current"/"preferred" messages (which don't apply to unassigned modes) and the [+-][HV]Sync flags which i assume were just forgotten to add to the unassigned outputs)
the distinction between unassigned modes and modes assigned to the last output can also be made in non-verbose mode, where the unassigned modes are shown in a more detailled way (as in verbose); nevertheless, the same message should also be shown there to avoid confusion.
while the overall severity of this is rather low, this is a severe program for tools that parse xrandr output (which is, i have to admit, not what xrandr is designed for).
Version: git