| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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.
|
|
|
|
|
|
| |
I love (neo)mutt to death, but the fact that it still doesn't have
modern color support drives nuts. Aerc seems like a viable alternative
MUA, so I'll be testing that now for a while.
|
|
|
|
| |
This is oddly calming.
|
|
|
|
|
| |
I like the idea of not having to constantly keep colorschemes up to
scratch manually.
|
|
|
|
|
| |
Most of my machines now have AMD GPUs in them, and this is useful when
offloading compute workloads onto them.
|
|
|
|
| |
This is useful on so many levels when one lives in the terminal.
|
|
|
|
|
| |
This tiny tool is pretty neat for quick, selective, and colorful DNS
output.
|
|
|
|
|
| |
A few things have changed since the recent NixOS 21.05 release. Mostly
naming stuff, so nothing dramatic.
|
|
|
|
|
| |
There is still an issue open for this on the nixpkgs GitHub, this is
just a workaround until it's resolved.
|
|
|
|
|
|
| |
I _really_ dislike having to run a browser to use a network that is
inspired by IRC, but here we are now. I sincerely hope someone comes up
with a useful terminal-focused client. No, weechat doesn't count.
|
|
|
|
|
|
| |
This is such an incredibly useful and versatile tool for understanding
and working with colors. I've been using it so much that I'm adding it
permanently.
|
|
|
|
| |
Fantastic terminal multiplexer.
|
|
|
|
| |
A lovely CLI hex viewer.
|
|
|
|
| |
This is a nice pager optimised for git.
|
|
|
|
|
|
|
|
| |
- `irssi` has been replaced with `catgirl`
- `lynx` is not really needed and also there's `w3m`
- `macchanger` has not been used
- `zettlr` has been used via `nix run` and so it makes sense to have it
permanently
|
|
|
|
| |
I'll need this to generate assets for UE.
|
|
|
|
| |
Very intriguing new IRC client.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This isn't working for me right now. Various different issues are afoot.
For one, my new headset at work functions as expected, until I change
volume, either on the headset itself or via normal volume control. My
local MPD isn't working either since the switch and there doesn't seem
to be a way to replicate that functionality with `pipewire` right now.
While I'd be more than happy to look into it, as usual, right now is not
a good time.
This reverts commit 997cbff6504bcd6bbc2b9fc72fecf271508956b8.
|
| |
|
|
|
|
|
| |
Don't need these extra packages and I'm tired of i3lock-fancy being so
damn slow.
|
|
|
|
|
|
|
| |
This seems very neat, and after a brief test I'm going to see if I can
switch to it permanently.
This is also the beginning of my journey to move to sway eventually.
|
|
|
|
|
| |
Add i3 extraPackages `i3-auto-layout` and `rofi`. This is much saner
than shoving everything into systemPackages.
|
|
|
|
|
|
|
| |
The normal `tldr-c-client` from `tldr`'s own repository hasn't been
updated in about 5 years and there is a really annoying update bug that
has a fix but upstream has just "forgot" about it it seems. So, this
alternative works as expected and is written in Rust. Yay.
|
|
|
|
| |
This is pure screenshot-bliss.
|
| |
|
| |
|
|
|
|
|
|
| |
I'm a bit tired of polybar and am very interested in i3status-rust,
however, the latter isn't a perfect replacement yet, so I'm going to
continue experimenting with it.
|
|
|
|
| |
These are not needed nearly as much as they once did.
|
|
|
|
| |
Recommended by aszlig to switch from module to package.
|
|
|
|
|
| |
This led to an issue where `vim` and `vimdiff` were launched from two
different derivations.
|
|
|
|
| |
Might be less annoying that having to do things via the browser.
|
|
|
|
| |
I'm very happy with `alacritty`, so I'm dropping `termite`.
|
| |
|
|
|
|
| |
It's marked as broken and I've been using `smos` more lately anyway.
|
|
|
|
|
| |
I'm finding myself use containers more and more these days, primarily
for testing stuff, so it's useful to have the tools installed.
|
|
|
|
| |
Forgot I had this still in here.
|
|
|
|
|
|
|
| |
I'm not sure when this started, but `scrot -s` introduces artefacts in
the screenshot because the selection border is captured with the
screenshot which is pretty annoying. It looks like `maim` doesn't have
this issue.
|
|
|
|
| |
This is incredibly useful if you don't want to leave the terminal.
|
| |
|
|
|
|
| |
Neat. Like cat, just better in certain circumstances.
|
|
|
|
|
| |
This seems like an immensely useful tool in conjunction with
`taskwarrior`.
|
|
|
|
|
| |
Reat that muesli made this lovely little tool, so naturally had to add
it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package attributes for GSstreamer 0.x were dropped[1] a while ago,
so evaluating the packages no longer succeeds and instead we get an
error like this on Hydra:
error: undefined variable 'gstreamer' at .../profiles/packages.nix:129:7
Initially I was tempted to change this to use pkgs.gst_all_1.gstreamer,
but looking at the differences between the old pkgs.gstreamer, the new
package only contains the relevant libraries while the old one contains
a few binaries, namely gst-feedback, gst-inspect, gst-launch,
gst-typefind, gst-xmlinspect, gst-xmllaunch and all of them again with a
"-0.10" suffix.
All of these tools are development tools and should not be used in real
applications, for example from the manual[2] on gst-launch-1.0:
> Please note that gst-launch-1.0 is primarily a debugging tool. You
> should not build applications on top of it. For applications, use the
> gst_parse_launch() function of the GStreamer API as an easy way to
> construct pipelines from pipeline descriptions.
While environment.systemPackages does link other directories than just
$out/bin, the primary reason why you'd want to put something in there is
to make it available in the system's PATH.
When asking @devhell about this he didn't remember the exact reason why
he put gstreamer in systemPackages, so I can only *assume* it was
because of tools like gst-launch, which unfortunately even I can
remember seeing recommended (instead of eg. ffmpeg) in some dark corners
of the web.
So if this would be really about gst-launch, we would need to put in
pkgs.gst_all_1.gstreamer.dev into systemPackages, since the development
tools are now where they belong.
Given that @devhell doesn't know the reason anymore and *also* told me
to remove it *and* it's also just a development tool which is not
supposed to be used in production, I'm hereby removing the package.
Should there really be applications which rely on this, they should
hopefully break after this change so they can be fixed to not rely on
these development tools.
[1]: https://github.com/NixOS/nixpkgs/commit/4a4e642abaaa026b55f42248a7b
[2]: https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|
|
|
|
| |
This is really useful.
|
|
|
|
|
| |
Same look, but written in rust and the binary is smaller too, what's not
to like?
|
|
|
|
|
|
| |
I'm really not digging the fact that weechat _constantly_ changes stuff
in it's config directory. Makes keeping it under version control a pain
in the ass.
|
|
|
|
| |
This seems to be useful.
|
|
|
|
| |
This seems useful.
|