i3: 4.13 -> 4.14

[NeQuissimus]

Motivation for this change

Update

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
  • macOS
  • Linux
• Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
• 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.

---

[grahamc]

Is this a mass rebuild? LGTM at any rate.

[NeQuissimus]

@grahamc nox-review says it is not...

[Mic92]

definitely not a mass-rebuild.

[grahamc]

Interesting. Building the PR locally resulted in bootstrap compilations. Must be a local issue.

…

On Mon, Sep 4, 2017 at 1:20 PM Jörg Thalheim ***@***.***> wrote: definitely not a mass-rebuild. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#28976 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAErrEQ3XOg4CCioasvBqNL_pKnN2Xyoks5sfDFZgaJpZM4PMAqE> .

[Mic92]

When starting py3status from nix-shell. I get the error message, that i3status is not found. Probably this should be added to the PATH of the py3status command.

[NeQuissimus]

@Mic92 Have you used py3status with 4.13? It's build inputs seem strangely sparse to begin with...
I just left it the way it was...

[fpletz]

py3status also works standalone (-s), so adding i3status is not strictly necessary.

[teto]

it would be nice to have access to manpages. man i3bar doesn't work here but that might be because I use an overlay to compile i3 from a local repository (though I doubt so).

[NeQuissimus]

@teto I think we can solve that in a separate PR, I am not sure how involved that would be.

[fpletz]

@teto Fixed in 101a048.

[teto]

Cool thanks

[NeQuissimus]

@fpletz What a beast, just whips out the fix :D (Thx!)