| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Finally, fish won't crap out if an emoji is pasted
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
I find myself working more and more with TOML files these days.
Unfortunately neither `vim` nor `neovim` upstream have added support for
syntax highlighting of TOML files yet.
|
|
|
|
| |
Finally, a useful frontend.
|
|
|
|
|
|
|
|
| |
I no longer have a scanner that requires to have hplip and/or any of the
proprietary parts of it, so let's keep it out of the machine
configuration.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Workspace one is usually my "communications workspace" and since I've
been using Psi as my go-to XMPP client, it's a good idea to add it to
that workspace, even though I usually start it on that workspace anyway.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I already had this in my configuration.nix for quite some time and it's
part of my overly complicated[TM] audio setup where I combine multiple
speaker systems into one using two sound cards.
Since the mapping depends on the individual channels, it's very much
important to address the right sound card. So while I'm re-doing my
whole audio setup, I decided to get at least the udev part out of my
very messy configuration as a first start.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
| |
Frequent python 2.7 breakages in nixops stable are getting on my nerves.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As mentioned in the initial commit (e73fcff03faed773df2500965cb9c4a4fc),
the machine was only temporary as a substitute for tishtushi.
Since slylandro had a pretty slow dual core CPU and its own quirks, this
was never a long-term solution and for the time being my intentions are
to work with dnyarri's new hardware until I have a less annoying setup
when I'm on the road again.
While writing this message, slylandro just died a gruesome death with
"cryptsetup erase", followed by "blkdiscard" on the whole drive.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
| |
This reverts commit 8ee2e8ee99e566f007051b9d1b51f6a14eb7b5f0.
pass 1.7.4 is in nixos-unstable now, so these changes are necessary to
fix the build of pass.
|
|
|
|
|
|
| |
It's been a while since I last used this machine. At some point I need
to go through it with a fine-toothed comb, but for now these changes
will be enough.
|
|
|
|
|
|
|
| |
`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 helps quite a lot when working with colors.
|
|
|
|
| |
This is oddly calming.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 88f3e07f175c813cd33469e426f76d7815dd1389.
Since https://github.com/NixOS/nixpkgs/pull/126616 still isn't merged
and also not in the current NixOS unstable channel, we run into the
following evaluation error:
assertion '(dmenuSupport -> (((dmenu != null) && (xdotool != null)) && x11Support))'
failed at: (17:1) in file: .../pkgs/tools/security/pass/default.nix
I decided to re-revert this change, because the commit in question
(which undid the revert) did not specify a good reason for doing so and
right now the eval error breaks all machine channels on Hydra.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
| |
Another one of a series of aliases to rename, similar to the last few
commits. Unfortunately, I didn't evaluate the sandbox test to make sure
all the references were changed, so I missed the netcat one.
This time however, I evaluated the sandbox test with latest nixpkgs and
it went without errors.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Another alias that has been introduced not too long ago[1] and now more
closely resembles the actual command name. Since NixOS VM tests no
longer allow aliases, our sandbox tests did not evaluate anymore.
While at it, I also renamed all the other uses of the alias.
[1]: https://github.com/NixOS/nixpkgs/commit/726306003af21ade95b1908d1920ce9a0f9815bb
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
The pinentry_* variants are all aliases and the actual packages are
separated with a dash instead. Since NixOS VM tests no longer allow
aliases, we need to use the real package name instead to avoid
evaluation errors.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is another alias which got introduced in 2018, because the actual
command is "pkg-config" and so the package name containing a dash is
more reasonable.
The reason why I'm doing this is because NixOS VM tests now disallow
aliases and while the evaluation error in question only affected the
"gnupg" test, I decided to change all occurences in the event that we
might want to disallow aliases for things other than VM tests.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @sternenseemann for "opam-env"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to 4701a995cb865c5d7178f574a3eae5872595e768, where I replaced
the libtidy alias for html-tidy because it broke evaluation of the PSI
test, I found another test for nman which uses an alias.
The background is that aliases are now[1] no longer allowed in NixOS VM
tests and since "s6PortableUtils" is indirectly referenced, we get an
evaluation error on Hydra.
Using the unaliased name fixes evaluation and should not change anything
in functionality.
[1]: https://github.com/NixOS/nixpkgs/commit/3edde6562e19698da69a499881e0a2e4f5a497a2
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mainly to incorporate my latest fix[1] for OMEMO, so in theory
updating the plugins would have been sufficient. However, since I like
to eat the freshest set of new bugs, I also updated everything else
except the theme. The latter seems to be a bit more complicated, since
it changed the way they're building it so I skipped that for now.
[1]: https://github.com/psi-im/plugins/pull/91
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The first (small) part of this already started in commit
dc2ef245d76f900f174e87961a3d17e6aecbd6e2, where I switched from Intel
CPU microcode to AMD.
However, at that time the hardware was still on its way, so the actual
move didn't happen yet.
On June 4th 2021 at 17:22:41 CEST, I started to migrate to the new
machine by using my old spinning rust configuration and btrfs balanced
to NVMe-only.
This means that we now no longer need to use bcache, which was a 512 GB
SATA SSD, nor do we use a RAID10 configuration in btrfs. Instead, I've
switched to NVMe with RAID1 exclusively, so this removes BFQ, power
management workarounds and two devices.
Since my old graphics card didn't work with UEFI GOP, I also had to
switch to a newer one (which I wanted to avoid, but whatever...), so
instead of DVI and HDMI we're now exclusively on DisplayPort.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A recent change[1] disabled aliases by default in VM tests and since
libtidy actually has been an alias of html-tidy since 2014 it's a good
idea to use the actual non-aliased packaged.
Since I added my PSI build in 2019, I probably didn't check for whether
the package name in nixpkgs would be different while packaging and only
used the name as reported by CMake, thinking it would work (which it
did).
Disallowing aliases in VM tests however is a good change, so let's use
the real package name.
This should fix the evaluation of the Hydra jobset.
[1]: https://github.com/NixOS/nixpkgs/commit/3edde6562e19698da69a499881e0a2e4f5a497a2
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
| |
I like the idea of not having to constantly keep colorschemes up to
scratch manually.
|
|
|
|
|
| |
As it turns out, rocm isn't supported on integrated Ryzen GPUs. No point
of having it around on herja then.
|
|
|
|
|
| |
Most of my machines now have AMD GPUs in them, and this is useful when
offloading compute workloads onto them.
|
|
|
|
|
|
|
|
|
| |
Since this package is introduced via an overlay expression pulled in via
IFD, I can't really fix it. Since dhall-flycheck has already been
removed from all machines it was a part of, just remove it completely to
migitate this issue.
cc @Profpatsch
|
|
|
|
| |
This reverts commit c11bd9ec702c71e731cb14c26ff235ea1956a613.
|
|
|
|
|
|
| |
This reverts commit 1987f2d9a4b185dfa319763a67d527fd7ade4d83.
This is not even merged into master yet, pushed by mistake.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
|
|
|
| |
I've done this before with herja, and then forgot to update the others.
|
|
|
|
|
| |
A few things have changed since the recent NixOS 21.05 release. Mostly
naming stuff, so nothing dramatic.
|
| |
|
|
|
|
| |
I never finished that one.
|
| |
|
|
|
|
|
| |
The service hasn’t been working in a while, since I deploy manually.
No security updates for baba.
|