| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
Module for the foot (wayland) terminal emulator. Approach for this
module is to take advantage of toINI and freeform module types to allow
users to freely set any option while still offering some higher level
representations for fields where plain strings would be inconvenient.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
sterni's personal texlive.combine { ... }
|
| |
|
|
| |
sterni's patched pass with passmenu
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
pkgs/sternenseemann/emoji-generic: init at unstable-2020-11-22
|
| |
|
|
|
| |
This machine is no longer active and probably would have to be redone
completely should it be reactivated.
|
| |
|
|
|
| |
This machine has been replaced and now runs Windows for playing
minecraft mostly.
|
| |
|
|
|
| |
This machine is no longer active and not really feasibly usable with
NixOS since i686 support was dropped.
|
| |
|
|
|
|
|
|
|
| |
The kdeApplications attribute got removed from the top-level a while
ago, so the machines using the "managed" profile no longer evaluate.
Instead, the plasma5Packages exposes the same set of packages.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
| |
We originally needed it here to deploy it on the machine, but it’s set
up manually via the gitit repo default.nix for the time being.
|
| |
|
|
|
|
|
|
|
|
| |
I no longer use this plugin and since evaluation currently is broken
upstream (blocked by [1]), let's make sure that at least the rest of
Vuizvui continues to evaluate.
[1]: https://github.com/NixOS/nixpkgs/pull/109679
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Upstream is deprecating `stdenv.lib`, so let’s do the same.
|
| |
|
|
| |
Small script to deploy my machines.
|
| |
|
|
|
|
|
|
|
|
|
| |
skarnet thought it would be wise to completely change the skalibs
exec function interface without any backwards compat, so here we are.
Have to reverse the code a bit, because `xmexec0` is a recursive
`#define` pointing to `xmexec0_af`.
`record-get` gets a rust treatment, it doesn’t really need the C
interface just to exec into prog.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Shiny new machine needs NixOS love. <3
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 7b8164be35c9d82d6e7389a407150a9128f7fb0c.
From the upstream changelog:
> This is an important bugfix release that should resolve several
> outstanding issues and concerns. Since 1.10.0 was released was engaged
> in a lot of discussions and realized that compatibility is more
> important than we first thought. So we're rolling back some breaking
> changes and revise some parts of our roadmap. We will strive to remain
> compatible with other password store implementations - but remember
> this is a goal, not a promise. This means we'll continue using
> compatible secrets formats as well as GPG and Git.
As mentioned in the original commit, I'm still not entirely convinced
that my use case has a future with gopass, their decision to roll back
some of the breaking changes at least makes it possible for me to
upgrade to the latest upstream version without the fear of being locked
in into some gopass-specific format.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
| |
I've been experiencing some nasty tearing and flickering lately. This
was a good opportunity to also change some settings.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Injecting pre/post start scripts into services called
"btrfs-scrub-.service.service" isn't going to do a whole lot if the
actual service name is called "btrfs-scrub-.service".
During the last scrub I was wondering why caching got slow afterwards
and found out that the caching devices were filled with lots of
irrelevant data from the scrub. This led me to inspect what went wrong
and when checking the properties of the scrub service unit, I found out
that it never worked in the first place for the reason meantioned in the
first paragraph.
Actually using the right unit name helps a lot here, so onwards to the
next scrub in February :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Dumb wrapper around `nix-instantiate` for something I often need.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Small tool which takes a block of nix options that should produce a
script to run, and then calls the script with the rest of argv
e nix-run { -A foobar } a b c
calls `nix-build -A foobar && ./result a b c`.
|
| |
|
|
|
|
|
|
|
|
| |
This is a working PoC of specifying module configs as toml
configuration with simple to understand semantics.
Both the option definitions and the actual config values can be
specified via the toml DSL.
This is extremely happy-path for now, so errors are gonna be horrible.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has been laying around since a few weeks but instead of just using
a simple shell script wrapper (which I had in the first place), I
decided to directly patch the binary during rC3.
The main reason why I went this route was because in the long run we
want to have a generic implementation we can use to patch all sorts of
games, similar to what we have with monogame-patcher.
So the way the *current* patcher roughly works is by allocating an area
called "compost", which is then used as some kind of abstraction for
allocating code and data to be used for the references/logic that we
need to patch.
The latter involves patching XDG_DATA_HOME into the game and changing
the "/usr/share/factorio" path to use the ones within the store path
($out/share/factorio). Fortunately, Factorio already assumes that
everything within /usr/share/factorio (or our path for that matter) is
read-only, so we don't need to add extra code/conditions specifically to
handle that.
Patching both cases is made possible by patching a third location
(get_executable_name), which tries to get the current executable path
via several methods (using /proc/self/exe, running "ps", ...) at
runtime, which in our case is really unnecessary and a perfect
opportunity to replace the function logic by the hardcoded path and
using the rest of the function for our compost area.
While patching might sound straigtforward, I actually introduced two
little (but hard to debug) bugs, where I'm very grateful to all those
folks (you know who you are) at rC3 who were actually following along
and provided helpful input.
In the long term, the goal is to rewrite the patcher with more elaborate
type information (eg. right now function/opcode information is raw JSON)
and generalise it enough that we can use it to get rid of a few other
wrappers.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Since the goal of using `e` with argv is interactive execution of
block-style commands from the command line, the use of { and } for
blocks is sub-optimal, since bash (and ostensibly also fish) interpret
them as metacharacters and assign some semantics.
[ and ] on the other hand are not taken (apart from the `[`
executable, which is only relevant in command position and can always
be replaced by the `test` command). So we translate a stand-alone "["
argument to "{" and the same for "]"/"}", giving us a transparent
block syntax.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Often times I want to execute “block-style” programs directly, but it
is rather inconvenient to type out `execlineb -c "…"` every time, plus
-c wants the argv as a single string instead of an argv.
The alternative, using the block representation with leading spaces,
is even less ergonomic.
So instead of
execlineb -c "nix-run { -A pkgs.profpatsch.e ~/vuizvui } echo hello"
or even
nix-run ' -A' ' pkgs.profpatsch.e' ' /home/me/vuizvui' '' echo hello
I can now write
e nix-run { -A pkgs.profpatsch.e ~/vuizvui } echo hello
and it will work as expected (provided your shell expands inside {}
blocks, which bash does but fish doesn’t for some reason).
If no argument is passed, e falls back to opening a shell prompt.
|
| |
|
|
|
|
|
|
| |
I no longer use Taskwarrior and since my config.patch fails to apply in
the most recent release, I think it's time to finally remove it from my
workstation profile.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One thing that has annoyed me since quite a while but ultimately didn't
fix yet, was that the urgency hint was only set for one millisecond.
I don't know how this would look like in a desktop environment, but in
my environment the corresponding workspace only flashes red and then
turns back to blue (the default color) whenever I get a new message.
Since I do not constantly switch to Psi to check whether there is
something new, I sometimes responded very late to messages even though I
didn't want to (eg. not actively working on something).
Of course, I also don't want to be interrupted when I'm actually in
zone, but luckily the way urgency hints are displayed in my environment
is pretty unobtrusive and there is no flashing, blinking or even sounds.
So the only difference is that I do not need to switch to Psi anymore,
to check whether there are new messages.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This has been mentioned on Discourse[1] and since I have that game in my
GOG library, I just decided to package it.
I only went to the main menu and didn't actually play it, since I'm
somewhat time constrained at the moment. So this only is "for the sake
of completeness" :-)
[1]: https://discourse.nixos.org/t/nix-expression-for-downloaded-gog-game/10595/7
Signed-off-by: aszlig <aszlig@nix.build>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a common pattern I encounter on a daily basis, which involves
copy & pasting the store path of a failed build to "nix log".
Now the same is just a matter of running "nlast" and we get rid of the
useless copy & paste.
The way we do this does have a small goof: Using mtime (or really any
time, other than atime, which commonly is disabled) is not going to work
if we *repeat* an older Nix build, since this will only change the log
file but the prefix directory will be unchanged.
Since addressing this goof would most likely result in iterating through
*all* log files, I'm not doing it since I think it doesn't occur very
often in practice. If I happen to be wrong on that, we could still go
for the heavyweight solution.
Also, I went for implementing this in Python instead of a shell script,
because the latter would not only be less readable but also way slower
since we need to either fork out for every stat command or use ls and
head to figure out the newest file.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
| |
Recommended by aszlig to switch from module to package.
|
| |
|
|
|
|
|
|
|
|
|
| |
No particular reason, other than current Psi version "feeling" too old
and I'm feeling somewhat adventurous.
The usrsctp library is now needed for Jingle, so I added a small build
of it directly from master as well. Who wants old release versions,
right?
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the "cryptography" Python library is marked as insecure I'd have
several options here: Add an excemption for the library, switch to
NixOps 2.0 or entirely remove it.
I chose to do the latter, since on all of my deployments I currently use
a heavily patched NixOps version which is somewhat of a mix between 1.5
and 2.0 and the version used here in the workstation profile is unused
since ages anyway.
In case I really need to use nixops on any of my workstations again, I
could still resort to "nix run".
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
|
|
|
|
| |
Added this when contributing to a GDScript project and since I know a
few persons who implement their games using Godot, I might need to write
GDScript at some point in the future again, so the syntax highlighting
plugin comes in handy.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
|
|
| |
This led to an issue where `vim` and `vimdiff` were launched from two
different derivations.
|
| |
|
|
| |
Don't need these either really.
|
