| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
exit is the wrong thing in shell functions …
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is, in the widest possible sense, a revert of
e88fed18f499a3e8ac98c772bbb62f00d1f8d1d7, which was now a little over
two years ago.
Of course, lots of things have changed since then:
- this uses npins instead of niv, which is both simpler and still
maintained
- i haven't brought back the old deploy lib; I still use
deploy-rs (with some modifications) to deploy things
- if you actually use my stuff downstream, you can now use packages/ &
tests/ & modules/ as entry points directly, while still having some
control over inputs
- (since i also don't believe any downstream users actually exist, i've
not bothered to have a shim flake.nix so your stuff probably just
broke. well, it was an experimental feature, anyways)
- in general there's a lot more of the old-fashioned structure back
again, with default.nix files in subdirectories that form a
structure, not like how almost everything was just imported in the
one big flake.nix file
For people who are interested in also having a non-flake config similar
to this one, it's probably best to take a look at inputs.nix (and also
at npins, of course)
|
|
|
|
|
|
|
| |
this is the rust tool used by the french ministry for
transport (deployed at https://transport.data.gouv.fr/validation),
patched to not include the server mode it usually has (i don't want to
constantly compile another copy of actix-web)
|
|
|
|
|
|
|
|
|
|
|
|
| |
I discovered `guix pull --news` recently and realised I barely ever keep
up with nixpkgs's change logs, so here's a thing which might help to
change that. It's actually a little more general than I thought it'd
need to be — turns out that people do change old release notes items in
nixpkgs (mostly to update links), so it can format deletions as well.
(some vague inspiration was given by https://github.com/netj/markdown-diff)
It's a little cursed, but then so is using `lowdown` at all I'd say …
|
|
|
|
| |
because for some reason it's not there already
|
| |
|
|
|
|
|
| |
lowdown isn't very good, but at least it doesn't have any weird cloud
features (why is this the standard for things that show text??)
|
| |
|
|
|
|
| |
let's see if this hydra of mine is of any use :)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so I added a command to search though them :)
Should help whenever I'm not sure if I have cloned something already.
Intended usage is something like `cd (git where)`. It might be useful to
extend this so it doesn't assume everything has a remote called
`origin', but looks like my only three git repos which don't have
one (and which are not my own) where cloned via heartwood/radicle, and
I'm unlikely to need those again tbh.
… tbh, it might also be worth it to add a mass-fetch command? So much of
what I've cloned is just old stuff lying around …
|
| |
|
| |
|
|
|
|
|
| |
the tool is still a bit rough, but it should work well enough for actual
use (even if i have to restart xochitl afterwards)
|
|
|
|
|
|
|
| |
doggo is more maintained, can use IPv6, queries all nameservers at once
by default, and generally feels comfier.
(now if only it had a man page ..)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
for Chris Marten's logic course. Uses an unofficial version from github
since the actually released version is so old that the elisp code for
the emacs mode doesn't work with an up-to-date emacs anymore.
|
| |
|
| |
|
|
|
|
| |
something something nftables module obscurity
|
|
|
|
|
|
| |
turns out there's an issue for that:
https://github.com/sharkdp/bat/issues/2563
and even a hint in bat's README.md
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
experimental, will probably still break on some stations
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
this packages the heartwood cli tools, the radicle web interface, and
runs a small example deployment on chaski.
TODO: decide if i want to keep this thing, then add declarative config
of the web interface, `rad auth`, and the radicle node to a NixOS
module; the current state is kinda suboptimal to deploy.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|