public/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

nixos/doc: Improve release notes for xrandrHeads

Browse Source 
The xrandrHeads option has been there since a long time, so there is no
need to advertise it as a new feature.

Instead, let's focus on just what has changed, which is that we now
assign one head to be primary.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
This commit is contained in:
aszlig 2017-04-24 11:54:38 +02:00
parent 8266c89b55
commit d7a8876c13
No known key found for this signature in database
GPG Key ID: 1DE8E48E57DB5436
1 changed files with 19 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
nixos/doc/manual/release-notes/rl-1709.xml
View File

@ -19,12 +19,25 @@ has the following highlights: </para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
Xserver services module now allows one to specify configuration for each monitor. The module option <option>services.xserver.xrandrHeads</option> now
This is done via the xrandrHeads property. It is backwards compatible, so your causes the first head specified in this list to be set as the primary
existing configuration still works. You can replace each monitor designation with head. Apart from that, it's now possible to also set additional options
an attribute set containing the monitor designation, whether the monitor is the by using an attribute set, for example:
primary monitor, and extra configuration for that specific monitor. Only one <programlisting>
monitor can be the primary monitor. { services.xserver.xrandrHeads = [
"HDMI-0"
{
output = &quot;DVI-0&quot;;
primary = true;
monitorConfig = ''
Option &quot;Rotate&quot; &quot;right&quot;
'';
}
];
}
</programlisting>
This will set the <literal>DVI-0</literal> output to be the primary head,
even though <literal>HDMI-0</literal> is the first head in the list.
</para> </para>
</listitem> </listitem>
</itemizedlist> </itemizedlist>