-
-
Notifications
You must be signed in to change notification settings - Fork 15.5k
services.xserver.xautolock: add module #25578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
+73
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mic92
reviewed
May 9, 2017
}; | ||
|
||
locker = mkOption { | ||
example = "i3lock -i /path/to/img"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a sane default locker option for instances i3lock?
according to the man page it's xlock. Didn't know that, will add it as default :-)
… On 9. May 2017, at 10:43 AM, Jörg Thalheim ***@***.***> wrote:
@Mic92 commented on this pull request.
In nixos/modules/services/x11/xautolock.nix:
> + Whether to enable the notifier feature of xautolock.
+ This publishes a notification before the autolock.
+ '';
+ };
+
+ time = mkOption {
+ default = 15;
+ type = types.int;
+
+ description = ''
+ Idle time to wait until xautolock locks the computer.
+ '';
+ };
+
+ locker = mkOption {
+ example = "i3lock -i /path/to/img";
Is there a sane default locker option for instances i3lock?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
@Mic92 done. |
fpletz
approved these changes
May 10, 2017
is there anyone else who might be able to test this? :-) |
Basic setup works for me. |
is there anything missing from my side or can this be merged? :-) |
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
6.topic: nixos
Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS
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.
Motivation for this change
I currently use
xautolock
for autolocking things.However I'd like to have a declarative module rather than a hacked configuration in the
sessionCommands
option of thedisplayManager
.I tested it using the following configurations:
I tested it using the following command:
Note:
I checked the
xsession
file and it seemed to work for me, however it would be nice if someone could test it before merging :-)Things done
(nix.useSandbox on NixOS,
or option
build-use-sandbox
innix.conf
on non-NixOS)
nix-shell -p nox --run "nox-review wip"
./result/bin/
)