| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
also enables debug feature on kernel
|
| |
|
| |
|
| |
|
|\
| |
| | |
nixos: doc: implement related packages in the manual (again)
|
| |
| |
| |
| | |
This is an attribute path example of `relatedPackages` option usage.
|
| |
| |
| |
| | |
This is a trivial example of `relatedPackages` option usage.
|
|\ \
| |/
|/| |
yabar: add module
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To make the configuration of `yabar` more pleasant and easier to
validate, a NixOS module will be quite helpful.
An example config could look like this:
```
{
programs.yabar = {
enable = true;
bars.top.indicators.exec = "YA_DATE";
};
}
```
The module adds a user-controlled systemd service which runs `yabar` after
starting up X.
|
|\ \
| | |
| | | |
nixos: sg/newgrp should always be available, not chfn
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
sg and newgrp only changes the current user session and should be
available to users even if the "users.mutableUsers" option is set.
These are common, useful commands.
chfn does modify the /etc/passwd GECOS field which is also controlled
by the option "users.users.<name?>.description", so it's less
appropriate to make it available when "users.mutableUsers" is set.
However, because CHFN_RESTRICT in login.defs is never set in current
NixOS the chfn functionality is never available to users anyway and
may as well have its SUID disabled, as only root is able to use it.
This is recommended in the chfn man page in this case.
|
|\ \
| | |
| | | |
nixos/less configure less with module
|
| | |
| | |
| | |
| | |
| | | |
Rather than a custom script the less config now uses the lesspipe
package config by default.
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| |
| | |
docbook interpreted this as a tag and this sounded as if the option
defaulted to putting the cached directory into the nix store.
cc @Ma27 @fpletz
|
|/
|
|
|
| |
The default cache directory set by oh-my-zsh is $ohMyZsh/cache which
lives in the Nix store in our case. This causes issues with several
completion plugins provided by oh-my-zsh.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This'll hopefully make it a bit easier to get started with Sway and make
some things about the module more obvious.
|
|\
| |
| | |
nixos/ccache: init
|
| | |
|
| |
| |
| |
| | |
Probably only relevant for a quick testing setup and NixOS VM tests.
|
| | |
|
|\ \
| | |
| | | |
nixos: doc: implement related packages in the manual
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* bemenu: init at 2017-02-14
* velox: 2015-11-03 -> 2017-07-04
* orbment, velox: don't expose subprojects
the development of orbment and velox got stuck
their subprojects (bemenu, dmenu-wayland, st-wayland) don't work correctly outside of parent projects
so hide them to not confuse people
swc and wld libraries are unpopular and unlike wlc are not used by anything except velox
* pythonPackages.pydbus: init at 0.6.0
* way-cooler: 0.5.2 -> 0.6.2
* nixos/way-cooler: add module
* dconf module: use for wayland
non-invasive approach for #31293
see discussion at #32210
* sway: embed LD_LIBRARY_PATH for #32755
* way-cooler: switch from buildRustPackage to buildRustCrate #31150
|
| | |
| | |
| | |
| | | |
https://github.com/scop/bash-completion/blob/fbd52a5e31747beb4974da97b9d3ed4f6ceb7a61/bash_completion#L2070-L2078
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As described in detail here: https://github.com/NixOS/nixpkgs/issues/32533
bash will load completion scripts in $p/share/bash-completion/completions/ on
startup instead of letting bash-completion do it's lazy loading. Bash startup
will then slow down (very noticeable when bash-completion is installed in a
profile).
This commit leaves loading of scripts in the hands of bash-completion,
improving startup time for everyone using `enableCompletion`.
fixes #32533
|
|\ \
| | |
| | | |
sway module: passthrough sway binary when needed
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The bash module currently sets the `/etc/inputrc` unconditionally,
which prevents easy user override. This commit lowers the priority of
the setting to "option default" level, which allows a user to override
the value using either
environment.etc."inputrc".text = …
or
environment.etc."inputrc".source = …
|
|/ /
| |
| |
| |
| |
| | |
Simply a small inconsistency I picked up when reading that file.
fixes #31795
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
5a5db609e5bd83bc589f36eef394f3ad172d6648 disabled it by default, which
may have been unintentional. mkEnableOption considered harmful.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Looks trival, but it is easy to make the mistake
to add linuxPackages.bcc to systemPackages,
which breaks if the not the default kernel is used.
|
| | |
|
|\ \
| | |
| | | |
npm module: add npm module for global npm config
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
programs.zsh: move evlauation of `${zshAliases}` after `cfg.interactiveShellInit`
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`cfg.interactiveShellInit`
`cfg.interactiveShellInit` is used by modules like
`programs.zsh.oh-my-zsh`. This means that all aliases defined in
`programs.zsh.shellAliases` might be overriden which is highly
unpredictable
|