| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 seems useful.
|
|
|
|
| |
Stuff like `virt-manager` has broken buttons.
|
|
|
|
|
|
|
|
| |
I've had this in my configuration.nix for a while and since I got used
to it, I think it's a good idea to enable both Nix Flakes and the "nix"
command by default for all my machines.
Signed-off-by: aszlig <aszlig@nix.build>
|
| |
|
| |
|
|
|
|
| |
Also add the service to legosi so I can use it from the weechat user.
|
|
|
|
| |
I'm fairly certain this isn't needed anymore.
|
|
|
|
|
|
|
| |
According to [1], `udev` has gained native support for FIDO security
tokens, and subsequently has been removed upstream.
[1]: 89c3e73dad0970b26183e415555fb0379ba33e7a
|
|
|
|
|
|
|
| |
As already stated otherwise in this log, it's back, so reverting the
removal.
This reverts commit 54b3f8ac7da02738be6919d05ae12d5c14796e3f.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
| |
|
|
|
|
| |
I shouldn't be working today I think.
|
|
|
|
| |
Duh.
|
|
|
|
|
| |
Replacing the simple inclusion of some programs in packages with
their respective programs.* equivalent.
|
|
|
|
| |
Aquired by Zoom, no thanks.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Knew I forgot something in the last clean-up.
|
|
|
|
| |
Still a continuation of some housekeeping.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In 7faaaab0af1e30bdfb72eca02abdfe92efefe4e0, I've changed the TERM
variable to contain "xterm-256color".
However, in our shell initialisation, we check whether $TERM is "xterm"
rather than whether $TERM *starts* with xterm.
Doing the latter fixes title setting and home/end keys in Vi normal
mode.
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>
|
|
|
|
|
| |
Unfortunately, development has seemingly ceased and has been marked as
insecure in aa80b4780d849a00d86c28d6b3c78a777dd02e9a.
|
|
|
|
|
|
|
| |
This option has been dropped upstream in
4732f59226a21b01d630c7ef4fb884bbfbe7dc83
Cc: @aszlig
|
|
|
|
|
|
|
| |
Since the latest update to `0.4.0` `lightdm` has added some more
fine-grained options to how the greeter behaves. In this case it added a
border around the password input box which doesn't look nice, so I'm
making it vanish here.
|
|
|
|
|
| |
With VirtualBox gone, I should be able to use the latest Linux kernel
again. Yippie!
|
|
|
|
|
|
|
|
|
| |
I've been trying to get away from VirtualBox for quite some time now.
unfortunately work has been preventing me from ditching it. I've been
doing some tests with virt-manager and, for now, I think it might be an
okay replacement. The only problem is that I've not found a way to
similarly export/import VMs in a convenient fashion which VirtualBox
offers.
|
|
|
|
|
| |
Having added nerdfonts was a bad idea because it's 5G apparently. Let's
not do this to aszlig's hydra.
|
| |
|
|
|
|
|
|
|
|
|
| |
I'm quite tired and bored of things like [1].
I can't find evidence that Brave has implemented this, so Brave will
replace Chromium.
[1]: https://www.chromestatus.com/feature/4733392803332096
|
|
|
|
| |
Small but still valid step towards more de-DRYing.
|
|
|
|
|
| |
VBox doesn't build with the newest Kernel. So, best to stick with the
old 5.4 for now.
|
|
|
|
|
|
|
|
|
|
|
| |
When fixing the eval error in 67e921d264c7832ac97e39ef73df760a20ad2b47,
I forgot about the fact that overrideAttrs doesn't reside in lib but
instead is a package attribute.
Since using "with lib;" is making it harder to quickly catch eval
errors, I also removed it from the module.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package no longer[1] uses an installPhase but instead the same is
now in postInstall. Since that module is pretty old I didn't use a
fallback to an empty installPhase, so the evaluation fails now.
Using postInstall along with a proper fallback should fix this, although
I haven't tested whether $out/etc/mpv/mpv.conf is still recognised by
mpv nowadays, we'll see...
[1]: https://github.com/NixOS/nixpkgs/commit/542d7589568c2f3c6ac58c6e307
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since I'm using Vi keybindings, pressing the Escape key is something I
do rather frequently. Having to wait for roughly a second after that
gets pretty annoying after a while, so let's set the timeout to 0.01
seconds.
This should usually be "small enough" to not interfere with other key
sequences resulting in escape characters, but let's see how this will
play out after a while.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
| |
Since more and more "Ultra HD" videos are out there, it really doesn't
make any sense to play such big resolutions if the monitor only is a
1080p display.
Signed-off-by: aszlig <aszlig@nix.build>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since a while[1], the services.xserver.displayManager.auto option is
deprecated. Since first of all SLiM got removed and now every display
manager supports auto-login, I switched the labtops module to use the
LightDM implementation.
Since the common x11 test module still exposes a similar interface, we
only need to use the same options from the test-support option, which
should hopefully be a "sane default" suitable for tests.
[1]: https://github.com/NixOS/nixpkgs/commit/c95612a5a2d4bd93011c042066c
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Trying to get around to cleaning out packages I don't need on a normal
basis, this is the start of a number of future commits that will be
dealing with cleaning up and optimising my package usage.
|
| |
|
|
|
|
|
|
| |
Fixes the evaluation warning.
cc @aszlig @devhell @sternenseemann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
The option has been moved[1] out of services.gnome3 since quite a while,
so let's actually use the new option "services.gvfs.enable" instead.
[1]: https://github.com/NixOS/nixpkgs/commit/67ad8a788fe0a8c22910d68d470416b6f5626740
Signed-off-by: aszlig <aszlig@nix.build>
Reported-by: @dwenola
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|