| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
| |
Pretty sure I don't really need this anymore. Might be wrong, we'll see.
|
|
|
|
| |
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.
|
|
|
|
|
| |
This package doesn't currently pass its tests and I'd like to not be
blocked from upgrading my system.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
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>
|
|
|
|
| |
The output is a bit cleaner and overall it seems to execute faster.
|
|
|
|
| |
Neat `ps` alternative.
|
|
|
|
| |
Seems that it suffered the same fate as `pastel`, for now.
|
|
|
|
|
|
|
| |
- `rq` is similar to `jq` but works with more types
- `watchexec` is neat to execute stuff on file change
- `wuzz` is a bit like burpsuite, but on the commandline
- `xsv` is just for CSV and has it's own specific functionality
|
|
|
|
|
| |
Always loved this font a little bit. Not as cool as the ultimate
oldschool fonts, but still.
|
|
|
|
| |
I don't know why, but I enjoy testing new tools replacing old tools.
|
|
|
|
| |
I'm not interested in shadows on everything.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regression introduced in 709e45c2a8c231201d3f67c6a954021ca2a5f796.
With that commit I renamed the "config" option to be called "settings",
but not only that, the actual config *file* is now to be found in the
"configFile" option.
Unfortunately I forgot to change that reference, which caused an
evaluation error.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
While ncurses already has support for detecting direct color terminals,
a lot of applications out there do not yet query terminfo but instead
rely on some shady COLORTERM environment variable. While I don't really
like that approach, patching XTerm to set that variable currently is
better than patching all the applications to query terminfo.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far, the TERM environment variable has been set to xterm-256color,
but in reality newer XTerm versions already supported 24bit colors so
setting this to xterm-direct results in using the right terminfo entry
for our terminal.
To make sure this is really the case, let's explicitly set directColor
to true, because while it is enabled in nixpkgs by default it is however
a compile-time option and could possibly be disabled.
Additionally, Vim is now looking pretty gruesome because my colorscheme
so far has used colors for 16-color terminals and I don't particularly
like the GUI colors. I added a few fixups for the color scheme to
address that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I haven't used the alias since a long time as it is probably apparent
due to the hardcoded "14.04" version of NixOS and given that I didn't
update the alias also speaks volumes about how useful it is altogether.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using vimdiff3 as the merge tool for a long time, but while it
has worked fine for most conflicts, using diff3 makes the original lines
visible which I always viewed in a separate shell rather than inline in
the editor.
Switching this to diff3 should hopefully make merge conflicts more
convenient to solve from now on.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In RFC-0042[1], the structural settings are exposed via a "settings"
attribute, while in our module it's called "config". To make this less
ambiguous (since there is already a "config" attribute passed to
modules) and more in line with best practices, I renamed it accordingly.
Additionally, the configuration file is now generated via *defining*
another (read-only) option, which can be used by other modules to
reference the path. The previous way this has been done was using the
apply attribute to mkOption, which makes it really hard to access the
original attributes for these settings.
[1]: https://git.io/JcXmU
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
This gets rid of bringing all of the lib attribute into the scope of the
whole module and also refactors a bit of ugliness, for example we're now
using overrideAttrs instead of overrideDerivation.
In addition I've simplified the type for the configuration, which should
now make it possible to mix subsubsections with normal subsections.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
I know that both `nixops` and `blender/expat` fixes are in staging, so
I'm just reverting this one to ensure that eventually there will be
fresh build. Currently `pastel` isn't building, so there's little point
in trying to skirt around this.
This reverts commit 4f73711332cc2220333dcf3eaccdd74c8cc61e10.
|
|
|
|
|
|
| |
The dependency issue has been fixed, so back to using Blender! Whoop!
This reverts commit 41cc1ddf2c2c0f69737bfe9ca144f0d0d2f3a26c.
|
|
|
|
| |
I've gotten used to delta enough to not need the diff alias.
|
|
|
|
| |
I need something sane to control application/file handling.
|
|
|
|
| |
Hopefully more sane than `element-desktop`.
|
|
|
|
|
| |
So, `xh` is really great, but I was wrong in thinking it's a perfect
drop-in replacement for `curl`.
|
|
|
|
|
|
| |
I enjoyed `sxiv`, but there were a few things that bothered me. I've
just discovered `imv` (I think), and really like it's minimalism,
despite having pretty much all the features I'd want.
|
|
|
|
|
| |
It looks like `opencolorio` isn't building. This is unfortunate because
I really need Blender actually.
|
|
|
|
|
|
|
|
|
|
| |
It's not clear when the `certifi` PR[1] will be merged, and I don't want
to have to wait for a new hydra build because of it. `nixopsUnstable` is
unusable in its current from due to almost lacking documentation, and so
I have little choice but to remove `nixops` right now until `certifi` is
merged.
[1]:https://github.com/NixOS/nixpkgs/pull/127453
|
|
|
|
|
|
|
| |
NixOps 2.0 has zero documentation. It's not at all clear how to set this
up. Gonna have to revert after all. Great.
This reverts commit e8f2190048e98b98c7d47479a44448ee6297dd10.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Aerc didn't turn out to be an improvement. I do like some of its design
ideas, but overall it doesn't really make me want to swith away from
neomutt. I've sat down and actually went through the pain for trying to
configure neomutt's colors properly according to the `tender`
colorscheme I've become fond of. It's not perfect since I have to match
the closest colors in xterm space, which isn't perfect, and until
neomutt has proper color support this will have to do.
I've added notmuch to simply find email quickly and be able to tag them.
|
|
|
|
| |
Finally, a useful frontend.
|
|
|
|
| |
Frequent python 2.7 breakages in nixops stable are getting on my nerves.
|
|
|
|
|
|
|
| |
`grex`: A command-line tools for generating regular expressions from
user-provided test cases
`tokei`: A program that allows you to count your code, quickly
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
These tools are `modern` replacements for the tried and tested, if a bit
boring, *NIX tools that we all love. My motivation is to try these tools
out for an extended period of time and see how I get on with them.
In order to remind myself that a certain tool is installed I've added
some aliases. Let's see how this goes.
|