Skip to content

Add x11 service for unclutter-xfixes #18398

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

Closed
wants to merge 9 commits into from
Closed

Conversation

erikryb
Copy link
Contributor

@erikryb erikryb commented Sep 7, 2016

Motivation for this change

This is a service similar to the unclutter service, but for the new unclutter-xfixes. There is some effort to make unclutter-xfixes compatible with unclutter, but for now it is probably best to keep them as two different modules.

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • OS X
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

Sorry, something went wrong.

@mention-bot
Copy link

@erikryb, thanks for your PR! By analyzing the annotation information on this pull request, we identified @edolstra, @bjornfor and @offlinehacker to be potential reviewers

default = 1;
};

threeshold = mkOption {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo (one 'e' too many).

config = mkIf cfg.enable {
systemd.user.services.unclutter-xfixes = {
description = "unclutter-xfixes";
wantedBy = [ "default.target" ];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nitpick: Imo this should be graphical.target.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that makes sense. Better to be explicit.

@groxxda
Copy link
Contributor

groxxda commented Sep 7, 2016

We also might want some ordering After=display-manager.service and possibly Requisite=display-manager.service (?).

@erikryb
Copy link
Contributor Author

erikryb commented Sep 8, 2016

Why "Requisite" instead of "Requires"?

@groxxda
Copy link
Contributor

groxxda commented Sep 8, 2016

Well, in my opinion if display-manager is not pulled in on it's own, unclutter should respect that and just refuse to start.. PartOf or BindsTo could also be valid choices, that's why I added a ❓ 😉

@erikryb
Copy link
Contributor Author

erikryb commented Sep 8, 2016

I see. It seems that BindsTo is a stronger version of Requires, so
that should also not be used for the same reason. Am I correct in that
PartOf is a weaker version of Requisite, that is, does Requisite
also restart or stop unclutter when display-manager restarts or
stops? If so, I believe Requisite is the best option, as you first
stated.

On Thu, Sep 08, 2016 at 05:34:35AM -0700, Alexander Ried wrote:

Well, in my opinion if display-manager is not pulled in on it's own, unclutter should respect that and just refuse to start.. PartOf or BindsTo could also be valid choices, that's why I added a ❓ 😉

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#18398 (comment)

@groxxda
Copy link
Contributor

groxxda commented Sep 8, 2016

I did not try the exact behavior, but Requisite sounded appropriate to me. I expect clutter to fail anyway when display-manager stops / fails / restarts, so it's not really that important whether it's propagated by systemd. But feel free to try and report what happens 👍

Apart from this, if you look at the redshift service that's quite similar, it will get merged even if it's not perfect.. 😞

By the way: doesn't this need the DISPLAY variable set?

@fpletz fpletz added 6.topic: nixos Issues or PRs affecting NixOS modules, or package usability issues specific to NixOS 8.has: module (new) This PR adds a module in `nixos/` labels Sep 13, 2016
romildo and others added 4 commits November 1, 2016 17:06
pdfjam is included in texlive
fixes NixOS#19826
In category `tools`, subcategory `text`, add a package definition for
the program [`agrep`] [1] — "Approximate `grep` for fast fuzzy string
searching".

I have tested this patch per nixpkgs manual section 11.1 ("Making
patches").

[1]: <https://www.tgries.de/agrep/>
Fixes build against linux >=4.8

Full changelog at
https://git.lttng.org/?p=lttng-tools.git;a=blob_plain;f=ChangeLog;hb=13dc409a5ea439b96b805c3c71886a3fcfad18e8

Tested with nix-build -A linuxPackages.lttng-modules -A linuxPackages_latest.lttng-modules
@bjornfor
Copy link
Contributor

bjornfor commented Nov 6, 2016

Why did you close?

@erikryb
Copy link
Contributor Author

erikryb commented Nov 6, 2016

It was a mistake. I rebased my master branch and the pull request got closed. I guess that's why I should have used a dedicated branch for the pull request. How do I reopen it? Or should I just start a new pull request?

EDIT: Alright, I reopened the pull request, but I don't know why the other commits other than mine got included.

@erikryb erikryb reopened this Nov 6, 2016
@joachifm joachifm closed this in 2f0cc0d Nov 29, 2016
@joachifm
Copy link
Contributor

@erikryb I rebased & merged this at 2f0cc0d. Thank you

@erikryb
Copy link
Contributor Author

erikryb commented Nov 29, 2016

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 8.has: module (new) This PR adds a module in `nixos/`
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants