Journaling using Nix, Vim and coreutils
tangled.sh
Journaling using Nix, Vim and coreutils
1–10 of 65 posts
Re: Journaling using Nix, Vim and coreutils
#2(That said, yes, it's a nice journaling system)
Re: Journaling using Nix, Vim and coreutils
#3Re: Journaling using Nix, Vim and coreutils
#4Re: Journaling using Nix, Vim and coreutils
#5I don't see what nix is doing for you? There's vim, absolutely, coreutils (though I don't immediately see anything GNU-specific), and a tiny wrapper script that happens to be written in flake.nix but could trivially be factored out. I don't see anything that I wouldn't expect to run on, say, OpenBSD if you installed vim. (That said, yes, it's a nice journaling system)
nix shell 'git+https://tangled.sh/@oppi.li/journal'
It's massive overkill for a shell alias, but for a more complex project it can be very nice.
Re: Journaling using Nix, Vim and coreutils
#6what is this nix religion I keep hearing about
Honest answer though, it's a deterministic way of building up a computer/environment. Think pip/uv/packages.lock but for everything.
Re: Journaling using Nix, Vim and coreutils
#7I don't see what nix is doing for you? There's vim, absolutely, coreutils (though I don't immediately see anything GNU-specific), and a tiny wrapper script that happens to be written in flake.nix but could trivially be factored out. I don't see anything that I wouldn't expect to run on, say, OpenBSD if you installed vim. (That said, yes, it's a nice journaling system)
Re: Journaling using Nix, Vim and coreutils
#8I don't see what nix is doing for you? There's vim, absolutely, coreutils (though I don't immediately see anything GNU-specific), and a tiny wrapper script that happens to be written in flake.nix but could trivially be factored out. I don't see anything that I wouldn't expect to run on, say, OpenBSD if you installed vim. (That said, yes, it's a nice journaling system)
I guess this does ensure the key `journal` command works exactly the same because the dateutils binary will stay locked to the version in the `flake.lock`.
I would have assumed that nvim would also be locked because that's where I would expect more possible breaking changes with the existing special config.
With little tools/projects like these I could easily see months-years before it would get any active attention from me again (or simply I wouldn't be using it; so it doesn't matter).