| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
I find all of these interesting for different reasons.
|
|
|
|
|
|
|
|
|
|
| |
This has been renamed[1] to reflect the upstream name and since there is
no alias for the old name, we need to rename it as well to avoid
evaluation errors.
[1]: https://github.com/NixOS/nixpkgs/commit/41574158a07f3c6ab5853b316c2fe7ed18e6354b
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
It is quite useful. Nice to see there is a good one around for vim.
|
|
|
|
|
|
| |
I do have to work a lot with screenshots and being able to create small
gif animations, right there, without much hassle, is fantastic. This
tool is a nice complement to `flameshot`.
|
|
|
|
| |
Fast, straight-forward, no-nonsense `du -sh` replacement.
|
| |
|
|
|
|
|
|
|
| |
I'm an idiot, plain and simple. Obviously `pactl` is part of
`pulseaudio` and I need it to control the damn volume. Argh.
This reverts commit 3323d35a6b466aaf8d5ad5a4f0bbfaa9a2e224da.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since Vim version 8.2.3141, the following error is raised during
startup:
Error detected while processing .../share/vim/vim82/plugin/02tlib.vim:
line 109: E1208: -complete used without allowing arguments
The latest version of the tlib plugin provides a fix for the above
error, so I'm updating it to latest master.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Pretty sure I don't really need this anymore. Might be wrong, we'll see.
|
| |
|
|
|
|
|
|
| |
I didn't notice this at first, but `thermald` only really works for
Intel CPUs. This is an AMD machine, and the daemon can't find anything
to work with, so there's no point in keeping it enabled here.
|
|
|
|
| |
Yes, it's brittle and currently doesn't build.
|
|
|
|
|
|
|
|
| |
Since I regularly use this for recovering data from various hard drives
and it's also a good idea to have it at hand with no Internet connection
in case something bad[TM] happens, let's make it available everywhere.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
I've dropped MPD for local playback now, so perhaps this means I can use
it now as expected.
This also adds `pulseaudio` for `pactl` to work, and enables `rtkit`.
This reverts commit 1931d7ead73c9060e0d163073e091e028e7b5dfa.
|
|
|
|
|
| |
I've stopped using MPD for local playback, only because it's a bit
annoying to try and make it work with PA and PW.
|
|
|
|
| |
Still not giving up on a sensible markdown plugin.
|
|
|
|
|
| |
This package doesn't currently pass its tests and I'd like to not be
blocked from upgrading my system.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes the following eval error:
The option `services.paperless' can no longer be used since it's been
removed. The paperless module has been removed as the upstream project
died.
Users should migrate to the paperless-ng module (services.paperless-ng).
More information can be found in the NixOS 21.11 release notes.
We don't use paperless in any machines but since we're testing for NixOS
module option definitions, we're running into the eval error above.
Switching to paperless-ng should get rid of them.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
While I love the idea of being able to use different interfaces for my
music listening, I'm not sure it's really worth it locally anymore. I
have an MPD server running on the network, which I can still connect to
using `ncmpcpp` for example, but for local playback, such as at work,
there is no point really in keeping it around. For local playback on
`gunnr` I'll just find something else. This would also solve my previous
PipeWire problem.
|
|
|
|
|
| |
I'm a bit annoyed at how `geoclue2` has everything and the kitchen sink
enabled, so I'm refining it here.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
buildEnv is conservative with creating symlinks, i. e. it only creates
directories if it has to. Consequently if a directory is only present in a
single package in the environment, it'll be a symlink.
Enter: makewhatis(8), a tool that has never imagined a creation as accursed as
Nix or even NixOS. Thus it assumes that probably no one ever uses symlinks in
their man directory and if they do, it'll be to alias man pages. Consequently
it assumes that all symbolic links are files [1] and ignores them in the
normal mode because they are in the wrong place. To still be able to use
apropos(1) with POSIX man pages, introduce this shell hack to re-create the
symlinked directories before building mandoc's db.
[1]: See also
https://inbox.vuxu.org/mandoc-tech/bccac2cd-01b6-b349-86e5-de4066ed8dee@systemli.org/T/#u
|
|
|
|
| |
Can't believe I've fixed all those aarch64 failures without this so far.
|
|
|
|
| |
The READ_ALLOWED_PATH patch was applied 🥳
|
|
|
|
| |
https://inbox.vuxu.org/mandoc-tech/c9932669-e9d4-1454-8708-7c8e36967e8e@systemli.org/T/#m445439360d5fbe71849001e39ce1e78a8a7d024f
|
| |
|
|
|
|
|
|
|
| |
Nevermind, I did test it before adding it, but I didn't test everything,
and as it turns out it's not what I hoped it would be.
This reverts commit 45894282b28ff8dee8ed7f1a31710ddc6ce275a2.
|
|
|
|
|
| |
I'm working so much with markdown lately that I'd find it helpful if I
didn't have to think of every markdown rule myself.
|
|
|
|
| |
I'm used to `sd` enought now to not forget it in lieu of `sed`.
|
|
|
|
|
|
|
| |
Enabling tab colors like this throws an eval error. Don't have time to
look into it right now, so reverting by adding `any-nix-shell` instead,
which looks useful since the default bash prompt is rather primitive and
gives no info whatsoever.
|
|
|
|
|
| |
This was annoying me for the longest time, but now I have colors back
when ZSH tab completes paths.
|
|
|
|
| |
Looks useful, let's see.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If we use 256 color mode in XTerm, using LightBlue in Vim results in
0x5fd7ff but LightBlue in GUI mode will use 0xadd8e6 which has a low
contrast to the default color (0xbebebe).
Since my eyes are not getting better with age, I decided to go with the
old color code that provides better contrast even though I'm quite happy
with the rest of the "more nuanced" colors.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
calling `execlineb -c` has unfortunate quoting issues, cause for
cornercases like arguments that contain spaces or `"` the result would
be a completely broken command line.
Instead, let’s do our own block construction in a small rust
program (for speed). I tried implementing it in bash first but even
prepending spaces to a string is a complete waste of time in that
language.
|
|
|
|
| |
Interesting take on an `nmap` replacement.
|
|
|
|
|
| |
I'm really happy to have found `mnamer`, it's a bit like `beets`, but
for TV series and movies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I'm already using this config since a few months and since I'm slowly
getting used to it, let's try to make it the default for my workstation
profile.
Unfortunately, libgit2 uses the Git configuration from /etc, but our
configuration is directly patched into Git and not in /etc but in
"${pkgs.git}/etc", so we need to patch libgit2 to use the right
configuration file.
Another goof is that we can't use ${pkgs.delta} directly in our Git
configuration because it would introduce a circular dependency between
Git itself and delta (which uses libgit2 which in turn refers to
"${pkgs.git}/etc"), so for the time being I'm relying on $PATH for
delta.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
| |
Duh.
This reverts commit 2d8ad8d8d158f5c4d1e3085062ec4619a18416c9.
|
|
|
|
| |
There's really no need to keep this exposed on the internal network.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
I don’t remember why I set that limit, but it’s kinda silly since nix
uses all cores by default.
|
| |
|
| |
|
| |
|