| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
So far, the TERM environment variable has been set to xterm-256color,
but in reality newer XTerm versions already supported 24bit colors so
setting this to xterm-direct results in using the right terminfo entry
for our terminal.
To make sure this is really the case, let's explicitly set directColor
to true, because while it is enabled in nixpkgs by default it is however
a compile-time option and could possibly be disabled.
Additionally, Vim is now looking pretty gruesome because my colorscheme
so far has used colors for 16-color terminals and I don't particularly
like the GUI colors. I added a few fixups for the color scheme to
address that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
I haven't used the alias since a long time as it is probably apparent
due to the hardcoded "14.04" version of NixOS and given that I didn't
update the alias also speaks volumes about how useful it is altogether.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using vimdiff3 as the merge tool for a long time, but while it
has worked fine for most conflicts, using diff3 makes the original lines
visible which I always viewed in a separate shell rather than inline in
the editor.
Switching this to diff3 should hopefully make merge conflicts more
convenient to solve from now on.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In RFC-0042[1], the structural settings are exposed via a "settings"
attribute, while in our module it's called "config". To make this less
ambiguous (since there is already a "config" attribute passed to
modules) and more in line with best practices, I renamed it accordingly.
Additionally, the configuration file is now generated via *defining*
another (read-only) option, which can be used by other modules to
reference the path. The previous way this has been done was using the
apply attribute to mkOption, which makes it really hard to access the
original attributes for these settings.
[1]: https://git.io/JcXmU
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The previous commit introduced a few new eval errors, for example:
cannot find attribute `vuizvui.programs.flameshot'
This is because the actual attribute path is
vuizvui.aszlig.programs.flameshot and not the one above.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
The PSI and Flameshot tests so far weren't part of the channels of the
machines where I use both programs, so if one of those tests would have
failed the channels would have advanced regardless of that.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
So far I've almost exclusively used scrot for screenshots, but most of
the time I used an image manipulation program to pixelate stuff, add
descriptions or draw arrows.
Flameshot combines this in a single application, so I expect that from
now on I can spam-post screenshots in even a higher rate than before ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
The option has been renamed since a while[1] ago, so to get rid of
annoying warnings, let's actually switch to the new option name.
[1]: https://github.com/NixOS/nixpkgs/commit/c99bd9bedf7291390c28eddb31f
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been using this configuration since years already but so far it has
been residing in ~/.muttrc and I copied to new machines accordingly.
The reason why I didn't add it here was because the config was too ugly
and I never got so far as to properly re-do it.
Unfortunately, the config is still ugly as hell, but at least we now
generate it from a structured Nix format and also the IMAP/SMTP user and
server infos are now retrieved via gopass instead.
This also includes my small prank multipart/alternative filter, which
should hopefully "encourange" recipients to disable HTML
parsing/rendering.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The DOSEMU fonts we were using so far for CP437 were bitmap fonts only
and with no unicode support.
Luckily there is https://int10h.org/oldschool-pc-fonts/ - which is a
really cool font pack containing all the cool oldschool fonts that I
remember from my childhood and still use today for creating ASCII art.
Since we recently* hit the 21st century, I think it's about time that
even I should start having terminals with proper Unicode support. The
latter is already the case, but the glyphs just didn't display
correctly.
The font that I switched to (MxPlus IBM VGA 8x16) is using embededd
bitmaps, so I also enabled useEmbeddedBitmaps option, so that the font
still looks as crisp as the old DOSEMU font.
To make sure it really is the same font, I compared screenshots of all
the CP437 characters with the new font and they match the old font 1:1.
I also removed the liberation_ttf font, since it's already included by
the default NixOS font configuration.
* -> Your mileage may vary, but hey, the 90ies were yesterday, right?
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I regularily keep things in nix-env to see whether I keep using them and
"entry" is one of the little tools I ended up using quite regularily.
The program monitors a set of files via inotify and runs a command
whenever one or more of them change, which makes it quite useful for a
"change code, compile, run" cycle.
Upstream URL: https://eradman.com/entrproject/
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
From the release notes of Git version 2.27.0:
* "git pull" issues a warning message until the pull.rebase
configuration variable is explicitly given, which some existing
users may find annoying---those who prefer not to rebase need to
set the variable to false to squelch the warning.
This is exactly the warning which is annoying me all the time now, so in
order to get rid of it, let's explicitly set the default behaviour
(which is doing a recursive merge).
Just to be sure that I really want the default behaviour, I analysed my
shell history for invocations of "git pull" and only around 20% of the
invocations were with --rebase, 14% were with an explicit URL (but no
rebase) and the rest were recursive merges.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 64fdbcc7e0949a3d3bf1cee3361d5ebe5c56cc4c.
It seems that there is now[1] a maintained version of p7zip and since I
didn't get used to unar so far, I take this opportunity to switch back
to p7zip.
[1]: https://github.com/NixOS/nixpkgs/pull/90140
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The patch I added to xournal was for keeping the aspect ratio when
annotating PDFs with images. However, looking at xournal++ the aspect
ratio is kept by default when resizing via corners so the patch is not
needed.
Since I don't really care a lot whether it's xournal or xournal++ and as
long as it does the very little things I intend to use it for, I don't
mind if it has too many features for my taste.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
So far I've been fine with just everything using 16 colours, but since
I'm even using 256 colours in my own ASCII art spriting engine I think I
can safely enter the 90ies and get some more colours.
Of course, the XTerm version I'm using is already supporting 256 colors,
it's just that the terminfo entry doesn't say so.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A while ago, p7zip has been marked as insecure[1], and while I didn't
use p7zip for any real archives, I used it for unrelated things like
executables and ISO9660 images and of course occasionally also 7z files.
While I haven't done extensive testing with unar, it does seem to have a
similar feature set when it comes to non-archive formats and also has
support for 7z archives as well.
[1]: https://github.com/NixOS/nixpkgs/commit/aa80b4780d849a00d86c28d6b3c
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
This option has been dropped upstream in
4732f59226a21b01d630c7ef4fb884bbfbe7dc83
Cc: @aszlig
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The option services.xserver.desktopManager.default and
services.xserver.windowManager.default are deprecated since quite a
while[1], so let's use the displayManager.defaultSession option instead.
Additionally, there no longer is any need to explicitly disable the
"xterm" desktopManager, so I removed that option as well.
[1]: https://github.com/NixOS/nixpkgs/commit/8dc5ff7dcfd1c58c32004ffae25
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Package currently doesn't evaluate because:
> Package xpdf-4.02 in ... is marked as insecure, refusing to evaluate.
>
> Known issues:
> - CVE-2018-7453: loop in PDF objects
> - CVE-2018-16369: loop in PDF objects
> - CVE-2019-9587: loop in PDF objects
> - CVE-2019-9588: loop in PDF objects
> - CVE-2019-16088: loop in PDF objects
While this might be fixed in the future, I'm removing the package
anyway, because I'm using zathura for quite a while (since mid 2016 to
be exact) and never used xpdf a single time since then.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the following evaluation error:
The option `services.xserver.displayManager.slim' can no longer be
used since it's been removed. The SLIM project is abandoned and their
last release was in 2013.
Because of this it poses a security risk to your system.
Other issues include it not fully supporting systemd and logind
sessions.
Please use a different display manager such as LightDM, SDDM, or GDM.
You can also use the startx module which uses Xinitrc.
Here is the nixpkgs upstream pull request removing SLiM:
https://github.com/NixOS/nixpkgs/pull/73251
Since I was using a custom theme for SLiM and actually liked the
minimalism, it's probably time to start patching LightDM soon. For now
however, I'll stay with a default LightDM configuration and wait until
I'm getting annoyed :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the "Witchcraft Compiler Collection", which is VERY useful for
reverse-engineering, especially when looking back at the work I've done
with game packaging here in Vuizvui, I would have needed something like
this a ton of times.
I've mainly used radare2 for dissecting the binaries, but especially the
"Witchcraft Shell" is quite useful to have.
Thanks to @Profpatsch for pointing this out to me.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The upstream service was shut down at September 11th 2019, so there
really is no need anymore for this package.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The services.redshift.{latitude,longitude} options are deprecated and
the replacement for them are the location.{latitude,longitude} options
that have been introduced since a while[1].
Both of the new options now use floating point numbers instead of
strings, which I changed accordingly (and also rounded them a bit).
[1]: https://github.com/NixOS/nixpkgs/commit/c4de0bf49289bc6b1448420dea39d7a5b0f3c374
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After using Gajim for years now, I got really frustrated by all its
warts, which mainly boil down the lack of type safety and its
interactions with its plugins.
Of course, I could also rip apart the plugin mechanism and Nixify them,
but in the end, the issues would still persist without a myriad of
tests that I don't have time right now to write.
After discovering a while back that Psi development has gained some
activity I decided to take a look into it a few weeks ago and while
there is certainly always things I don't like about some detail, it's
IMO a way better base for my future XMPP client.
So goodbye Gajim and hello Psi :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
I no longer use last.fm nor do I use this project (even though it's my
own one), so let's remove it.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
When writing that module back then in 88a10f1a6e2ea172ff985f64bfcf82e2,
I had to work around a systemd limitation (which I need to check whether
this is still the case today) and hardcoded the user name for the time
being.
While it's still quite ugly, there was interest from @Profpatsch, so I
decided to add an internal option to change that username.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
The zswap module is essentially what I had here, so let's just use that
instead.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since kernel 4.18 contains the zstd compression module in the crypto
API, it really makes sense to use that instead of the default (lzo) as
it seems to have lower CPU usage with higher compression ratios.
Another change I've made is to use z3fold for the pooling, so that 3
pages are cramped into one page of the pool. I did also have a look at
zsmalloc, but it seems to come with the cost of additional CPU usage.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
Two of the applications I use (gpodder and gajim) use Gtk and the
default Adwaita theme is rather blinding me, especially at night.
So let's set the GTK_THEME environment variable globally.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
D'oh, I accidentally added the original package *after* creating the
patched one.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Even though gopass is more complex than pass, it's also less fragile
because it's written in a reasonably type-safe language rather than
being a giant shell script that relies on lots of external commands.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
The whole package actually, including the ncurses UI and web interface.
Not that I really need the UI/web stuff right now, but it might come in
handy later.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
| |
It's been ages since I needed to authenticate to SSHd via a password, so
let's actually make sure we only use pubkey auth by default. If we need
more than that we can still change the value to something else on a per-
machine basis.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The config.patch doesn't apply for Gajim 1.0 anymore anyway, so let's
throw everything away, including my custom config in order to start with
a new abomination.
With the new approach, I'm going to patch the configuration defaults
*directly* into Gajim, because one of the problems with the old approach
was that whenever specifics about a configuration value has changed, I
didn't get noticed by a patch failure.
So in the end the config I was ending up was a big mess.
I'm going to start this with a new unpatched version and someday get to
a patched version that I'm staisfied with... hopefully ;-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
I very rarely use this and if I want to I can still use nix run to bring
it in and it has been a lazy package anyway.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
| |
This one is an old leftover from where I ran patched versions of NixOps,
but nowadays it is already in <nixpkgs>, so no need to keep it around.
Other than that, with Hydra now running in restricted eval mode it will
run into an eval error.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
| |
I'm testing every fart that I push to nixpkgs, so why don't I test it
here as well? Dammit!
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
This was more or less accidentally leaked to PATH and got removed in
NixOS/nixpkgs@71a8dbb956f5735030cd3982263d72f1bffdae23, so let's add it
in again.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Since NixOS/nixpkgs@a43e33d0e48b2284ac3a2222d7f1965cef66f5e2 this is no
longer enabled by default so in order to, for example, restore card
volumes we need to have this enabled.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We no longer use the legacy SSH store protocol for taalo but the new
ssh-ng protocol, which makes the implementation of taalo-build a LOT
less clunky.
It also didn't make sense to have this as a NixOS module when we after
all just emit a static store path without any stuff depending on
configuration options.
The new implementation basically just wraps nix-build and nix-store -r
along with the right NIX_REMOTE variable.
With Nix 1.2 this can also be done with the new "nix build" command
using the --store option, but unfortunately "nix build" doesn't yet have
the same functionality as nix-build.
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch, @bendlas
|
|
|
|
|
|
|
| |
I'm no longer employed by RedMoon Studios, so while I still receive
email on this address, it makes more sense to move on to nix.build :-)
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
| |
The previous GnuPG key (4DFD43EC834B6901BDA2BAAC1DE8E48E57DB5436) was
subject to the ROCA vulnerability, so I had to revoke it.
For details about this vulnerability, please visit:
https://crocs.fi.muni.cz/public/papers/rsa_ccs17
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
It's a fast and less verbose alternative to find and while it won't
replace find entirely for me it certainly will be useful for less
complicated stuff or simple one-liners.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
Actually this is the only one workstation where I use gpodder, so let's
move it there and also don't make it a lazy package.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
| |
I might move to Firefox as my primary browser again. Apart from that, I
regularily use it anyway, so having it as a lazy package doesn't make
sense.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I tend to use it more frequently than I thought I would and it's quite
small, so let's make it the default for my workstations.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
| |
I'm not going to use this a lot, so let's not clutter up the closure
size with it, even though the package is actually quite small.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|
|
|
|
|
|
|
|
|
| |
Since version 4.0 of xpdf, the UI has vastly changed and the
configuration setting I'm using in this module no longer is necessary
for me. So let's drop the module altogether until I'm getting used to
the new xpdf and find new things I don't like :-)
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
|