| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This is not really to inform anybody about anything, but mostly to get
rid of the warning generated by `nix-build -A manual release.nix`.
|
|
|
|
|
|
|
|
|
| |
Apparently (probably since GNU came along) there are manuals for
different languages than english in share/man/$language. This adds
support for this in my mandoc module by allowing the user to freely
specify the manpath entries under $out.
> nmap(1) - Netzwerk-Analysewerkzeug und Sicherheits-/Portscanner
|
|
|
|
| |
This is pure screenshot-bliss.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The general consensus seems to be to use
vuizvui.user.<username>.<category>.<module name>
instead of
vuizvui.<category>.<user name>.<module name>
Things done to test this change:
* Checked build of machines.profpatsch.legosi.build
* Checked evaluation of machines.profpatsch.shiki.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>
|
|
|
|
|
|
|
| |
Due to a previous oversight hardware.opengl.enable = true; wasn't set
anymore (previously it was by programs.sway which has been replaced).
Thus sway couldn't load the necessary OpenGL driver's anymore after a
reboot.
|
|
|
|
|
|
| |
This reverts commit 5bd756eaf27882820cb59e0ecf9c305f08b3b3e3.
Committed more than I meant to.
|
|
|
|
|
|
|
|
|
|
| |
nixpkgs has removed flash support in chromium without replacement in
d55603f11d36ae38ca76dec8d95bc55d2115f104 following the removal in
upstream chromium M88, so I'm disabling it completely in
vuizvui.user.aszlig.profiles.managed to fix the evaluation of shiki
and brawndo.
cc @aszlig
|
|
|
|
|
|
| |
sway needs opengl driver's to be enabled and loadable in order to start.
I previously didn't notice this oversight as I still had them loaded and
did not reboot after the rebuild.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This module implements a drop-in replacement for documentation.man which
finally lets me get rid of pkgs.man-db. This is still to be considered
experimental as the required patch hasn't landed in upstream mandoc yet.
Should that happen, I'll try to contribute this module back to nixpkgs.
A more detailed description on the module and mandoc on NixOS can be
found at the top of modules/user/sternenseemann/documentation/mandoc.nix
|
| |
|
|
|
|
| |
machines/sternenseemann/wolfgang: refactor using new sway module
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
This led to an issue where `vim` and `vimdiff` were launched from two
different derivations.
|
|
|
|
| |
Don't need these either really.
|
|
|
|
|
| |
Nerd Fonts looks interesting and should replace most of the ones I
already use.
|
|
|
|
|
|
|
| |
I just like `tender` colorscheme too much, and also `dracula` didn't
work very well. Although most of my LaTeX work is done on Overleaf,
sometimes I do need some good local LaTeX support in vim, so let's give
`vimtex` a chance.
|
|
|
|
|
|
|
|
|
|
| |
I've been trying to get most of my environment directly configured via
my NixOS configuration rather than rely on my dotfiles repository, if
the program/configuration is well supported in NixOS.
Just like Vim, here too I'm relying more on NixOS' ZSH options, which
truly eliminates dependencies on external repositories or dotfile
setups.
|
|
|
|
| |
Might be less annoying that having to do things via the browser.
|
|
|
|
| |
I'm very happy with `alacritty`, so I'm dropping `termite`.
|
| |
|
|
|
|
| |
Now it's pretty much the way I want it.
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
The `sensible` plugin doesn't work for me. I think setting things
manually is probably better for now.
|
|
|
|
| |
It's marked as broken and I've been using `smos` more lately anyway.
|
|
|
|
| |
Fully automatic indentation, why not.
|
|
|
|
|
| |
I'm finding myself use containers more and more these days, primarily
for testing stuff, so it's useful to have the tools installed.
|
| |
|
|
|
|
| |
Forgot I had this still in here.
|
|
|
|
|
|
|
| |
This config works now. Huge thanks to aszlig for helping! This is only a
bare-bones configurations. There are some parts of SpaceVim I really
enjoy, so over time I'll try to get my Vim configuration to emulate
those parts.
|
|
|
|
|
|
| |
This is in preparation of me leaving SpaceVim behind and not having to
rely on external sources for certain programs, such as Vim, when
installing a new machine.
|
|
|
|
|
|
|
| |
I'm not sure when this started, but `scrot -s` introduces artefacts in
the screenshot because the selection border is captured with the
screenshot which is pretty annoying. It looks like `maim` doesn't have
this issue.
|
|
|
|
| |
This is incredibly useful if you don't want to leave the terminal.
|
| |
|
|
|
|
| |
Neat. Like cat, just better in certain circumstances.
|
|
|
|
|
|
|
| |
Well, that was a bit too hasty, I forgot that MPD runs as its own user
and therefore can't talk to pulseaudio if this isn't set.
This reverts commit dc4882e92f84c157d682b860365644ffd1f5c0d6.
|
|
|
|
|
| |
This seems like an immensely useful tool in conjunction with
`taskwarrior`.
|
|
|
|
|
| |
Reat that muesli made this lovely little tool, so naturally had to add
it.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The package attributes for GSstreamer 0.x were dropped[1] a while ago,
so evaluating the packages no longer succeeds and instead we get an
error like this on Hydra:
error: undefined variable 'gstreamer' at .../profiles/packages.nix:129:7
Initially I was tempted to change this to use pkgs.gst_all_1.gstreamer,
but looking at the differences between the old pkgs.gstreamer, the new
package only contains the relevant libraries while the old one contains
a few binaries, namely gst-feedback, gst-inspect, gst-launch,
gst-typefind, gst-xmlinspect, gst-xmllaunch and all of them again with a
"-0.10" suffix.
All of these tools are development tools and should not be used in real
applications, for example from the manual[2] on gst-launch-1.0:
> Please note that gst-launch-1.0 is primarily a debugging tool. You
> should not build applications on top of it. For applications, use the
> gst_parse_launch() function of the GStreamer API as an easy way to
> construct pipelines from pipeline descriptions.
While environment.systemPackages does link other directories than just
$out/bin, the primary reason why you'd want to put something in there is
to make it available in the system's PATH.
When asking @devhell about this he didn't remember the exact reason why
he put gstreamer in systemPackages, so I can only *assume* it was
because of tools like gst-launch, which unfortunately even I can
remember seeing recommended (instead of eg. ffmpeg) in some dark corners
of the web.
So if this would be really about gst-launch, we would need to put in
pkgs.gst_all_1.gstreamer.dev into systemPackages, since the development
tools are now where they belong.
Given that @devhell doesn't know the reason anymore and *also* told me
to remove it *and* it's also just a development tool which is not
supposed to be used in production, I'm hereby removing the package.
Should there really be applications which rely on this, they should
hopefully break after this change so they can be fixed to not rely on
these development tools.
[1]: https://github.com/NixOS/nixpkgs/commit/4a4e642abaaa026b55f42248a7b
[2]: https://gstreamer.freedesktop.org/documentation/tools/gst-launch.html
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @devhell
|