Branch: refs/heads/master
Home: https://github.com/NixOS/nixpkgs
Commit: bb6a5b079fe8c88a6e42c92179711b2d0a9a9842
https://github.com/NixOS/nixpkgs/commit/bb6a5b079fe8c88a6e42c92179711b2d0a9a9842
Author: Roger Qiu <[email protected]>
Date: 2017-04-21 (Fri, 21 Apr 2017)
Changed paths:
M nixos/doc/manual/release-notes/rl-1709.xml
M nixos/modules/services/x11/xserver.nix
Log Message:
-----------
nixos/xserver: Changed xrandrHeads to support corresponding monitor section
configuration in Xorg
Commit: 8266c89b55e3ae97ff635a0f9f8aee556ae7b384
https://github.com/NixOS/nixpkgs/commit/8266c89b55e3ae97ff635a0f9f8aee556ae7b384
Author: aszlig <[email protected]>
Date: 2017-04-24 (Mon, 24 Apr 2017)
Changed paths:
M nixos/modules/services/x11/xserver.nix
Log Message:
-----------
nixos/xserver: Fix up/refactor xrandrHeads option
Using invalid module options in the submodule isn't very nice, because
it doesn't give very useful errors in case of type mismatch, also we
don't get descriptions of these options as they're effecively
nonexistent to the module system. Another downside of this is that
merging of these options isn't done correctly as well (eg. for
types.lines).
So we now have proper submodules for each xrandrHead and we also use
corcedTo in the type of xrandrHeads so that we can populate the
submodule's "output" option in case a plain string is defined for a list
item.
Instead of silently skipping multiple primary heads, we now have an
assertion, which displays a message and aborts configuration evaluation
appropriately.
Signed-off-by: aszlig <[email protected]>
Commit: d7a8876c13f75e7a55e2f3cbc16346406e9abdf8
https://github.com/NixOS/nixpkgs/commit/d7a8876c13f75e7a55e2f3cbc16346406e9abdf8
Author: aszlig <[email protected]>
Date: 2017-04-24 (Mon, 24 Apr 2017)
Changed paths:
M nixos/doc/manual/release-notes/rl-1709.xml
Log Message:
-----------
nixos/doc: Improve release notes for xrandrHeads
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 <[email protected]>
Commit: 79e712822fcfe797c545e2db5bcef9a07b00b2e5
https://github.com/NixOS/nixpkgs/commit/79e712822fcfe797c545e2db5bcef9a07b00b2e5
Author: aszlig <[email protected]>
Date: 2017-04-24 (Mon, 24 Apr 2017)
Changed paths:
M nixos/modules/services/x11/xserver.nix
Log Message:
-----------
nixos/xserver: Document xrandrHeads.apply
It was asked by @CMCDragonkai to elaborate on that, so let's just do
this by actually providing a code comment.
Signed-off-by: aszlig <[email protected]>
Commit: 9dca737d6269759745c9e68ea462446cde4d9be9
https://github.com/NixOS/nixpkgs/commit/9dca737d6269759745c9e68ea462446cde4d9be9
Author: aszlig <[email protected]>
Date: 2017-05-02 (Tue, 02 May 2017)
Changed paths:
M nixos/doc/manual/release-notes/rl-1709.xml
M nixos/modules/services/x11/xserver.nix
Log Message:
-----------
Merge pull request #15353 (improve xrandrHeads)
When you have a setup consisting of multiple monitors, the default is
that the first monitor detected by xrandr is set to the primary monitor.
However this may not be the monitor you need to be set as primary. In
fact this monitor set to primary may in fact be disconnected.
This has happened for the original submitter of the pull request and it
affected these programs:
* XMonad: Gets confused with Super + {w,e,r}
* SDDM: Puts the login screen on the wrong monitor, and does not
currently duplicate the login screen on all monitors
* XMobar: Puts the XMobar on the wrong monitor, as it only puts the
taskbar on the primary monitor
These changes should fix that not only by setting a primary monitor in
xrandrHeads but also make it possible to make a different monitor the
primary one.
The changes are also backwards-compatible.
Compare: https://github.com/NixOS/nixpkgs/compare/beff1984f4c8...9dca737d6269_______________________________________________
nix-commits mailing list
[email protected]
https://mailman.science.uu.nl/mailman/listinfo/nix-commits
