about summary refs log tree commit diff
path: root/modules/user/aszlig/profiles/workstation
Commit message (Collapse)AuthorAgeFilesLines
* workstation: Don't wait for all NICs to be onlineaszlig2023-07-151-0/+4
| | | | | | | | I occasionally run wireguard setups, sometimes broken beyond repair, and I really don't care whether those are online or not as long as *any* interface is alive. Signed-off-by: aszlig <aszlig@nix.build>
* packages: Replace youtube-dl with yt-dlpaszlig2023-06-021-1/+1
| | | | | | | | | | I had yt-dlp in my local Nix profile since quite a while and didn't use youtube-dl at all since months. It's been so long that I actually forget about that, thinking I already did this very change already. Turns out, that I didn't, hence this commit. Signed-off-by: aszlig <aszlig@nix.build>
* treewide: address rename of boot.cleanTmpDir optionsternenseemann2023-05-141-1/+1
| | | | cc @Profpatsch @aszlig
* slylandro: Remove hidpi specific settings for nowaszlig2023-04-091-5/+1
| | | | | | | | | | | | | | | | | This reverts commit c88fd9eaa12c8a3c06502b09c2056d3c91421952. The hardware.video.hidpi.enable option was removed a while ago[1] because it's not clear what a single boolean option should mean, so it doesn't make sense anymore to make any of our options depend on it. Forthermore, I'm experimenting with different Wayland compositors at the moment and most of the stuff that I did here is for Xorg. I expect most of the stuff to be gone when I'm settled with a Wayland setup that works for me. [1]: https://github.com/NixOS/nixpkgs/pull/222689 Signed-off-by: aszlig <aszlig@nix.build>
* workstation/packages: Remove Python 2 stuffaszlig2023-01-171-4/+3
| | | | | | | | | | | | All the packages (hetzner, pep8 and polib) have Python 3 support but I've used the Python 2 versions of them. Since Python 2 is failing evaluation because it's marked as insecure, let's switch to the Python 3 versions. I also removed the the Python 2 interpreter, especially since I haven't been using it for quite a while. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Switch to Nix-managed Firefoxaszlig2022-10-271-1/+1
| | | | | | | | | | | | | | I had this laying around locally for a year now and I'm still not really happy with some things, for example not having yet full source builds of the extensions and a few config options not yet managed by Nix (eg. search engines). However, since Firefox takes a while to build it's a bit tedious to always do it directly (and locally) after I update my machines. Having this part of my workstation profile should make sure that my version of Firefox is available at all times. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation/git: Sort branches by dateaszlig2022-10-091-0/+1
| | | | | | | | When you have a lot of branches it's sometimes tedious to find out the ones you've been working on recently. Sorting the branches by committer date by default should make it more obvious. Signed-off-by: aszlig <aszlig@nix.build>
* Fix attribute name for man-pages-posixaszlig2022-09-261-1/+1
| | | | | | | | | | | | The posix_man_pages attribute has been renamed in nixpkgs[1] to man-pages-posix to more closely match the upstream name. This now[2] results in an evaluation error. [1]: https://github.com/NixOS/nixpkgs/commit/4461230cc5e11952407f8ddd205 [2]: https://github.com/NixOS/nixpkgs/commit/d06207386df9a53fe01f8a30130 Signed-off-by: aszlig <aszlig@nix.build> Cc: @devhell
* radare2: Add patch to default to AT&T ASM syntaxaszlig2022-09-181-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some personal history on this: I started to get used to AT&T syntax because it's the default in GDB and used that ever since until I one day starting to do some more reverse engineering using radare, which defaults to Intel syntax. Ever since then probably my most used command in GDB was "set disassembly-flavor intel" (because I was to lazy to add it to the config) because I constantly got confused by the source/destination operand swaps. This even happened during live reverse engineering at rC3 where I was confused about some function logic only to find out that I was viewing in AT&T syntax. Fast-forward to today: I'm debugging some application using WINE and winedbg uses AT&T syntax, which I didn't like at first. After reflecting on this for a while, I thought it would probably be better to get used to AT&T syntax again and switch everything to use AT&T for the following reasons: * Operands are more natural to read, since most libraries/APIs in higher level languages do it like this (well, except memcpy, strcpy, etc... maybe I now get confused by libc functions...) * AT&T syntax feels less verbose, for example "mov ecx, dword [eax]" is just "movl (%eax), %ecx" This very commit makes sure that radare2 now defaults to AT&T syntax instead of eg. ensuring that GDB uses Intel syntax by default. Signed-off-by: aszlig <aszlig@nix.build>
* workstation/packages: Add zbar to system packagesaszlig2022-09-111-0/+1
| | | | | | | | | | | Just had to scan the credentials for a Wi-Fi access point and they were only available via QR code, but was unable to make it available via Nix shell because I had (for obvious reasons) no access to the Internet. Adding zbar to all my machines will ensure that something like this won't happen again. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Use oldschool font pack from nixpkgsaszlig2022-09-051-11/+1
| | | | | | | | | Back then when I added the font pack in 0171f8d895efd46300ba01c6adeb7aa, version 2.0 was not yet merged to nixpkgs. This has happened in the meantime and the current version is version 2.2 and I also do not see any reason to keep the 2.0 version in Vuizvui. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Use autoLogin on LUKSaszlig2022-09-051-19/+28
| | | | | | | | | | | | | | | | | After countless boots with unlocking my LUKS containers and thereafter logging in via lightdm I started to wonder whether it really makes sense to do the latter. All of my workstations are single-user, I usually don't switch my session type (and even if, then via system configuration) and if someone manages to unlock my LUKS containers, it's really trivial to circumvent the user authentication. So if I'm not forgetting about something big[TM], the only purpose this additional auth serves is me being annoyed for no reason, so let's disable it if the configuration indicates that LUKS is used. Signed-off-by: aszlig <aszlig@nix.build>
* Use a font point size of 10 on hidpiaszlig2022-09-051-1/+4
| | | | | | | | | With my new laptop, a font size of 12pt is rather large and given that hidpi displays usually have a quite large resolution (the name might hint at that), we don't necessarily need to use embedded bitmaps anymore which was one of the reasons why I used a point size of 12. Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Add perf to systemPackagesaszlig2022-08-151-5/+8
| | | | | | | | I use perf on a regular basis and since it's dependant on the currently running kernel version, it' just makes sense to have it available at all times rather than "nix run" it with the right kernel version. Signed-off-by: aszlig <aszlig@nix.build>
* packages: Replace jwhois by whoisaszlig2022-08-151-1/+1
| | | | | | | | | | | | | | | | The upstream project seems to be no longer maintained[1] and the last release from 2005 contains a whole bunch of outdated NIC information so that it became pretty annoying to use. Back then jwhois was the only whois client packaged in nixpkgs, so this might be the reason why it ended up in my setup in the first place. The "whois" package on the other hand seems to be actively maintained and works well for the domains I care about. [1]: https://github.com/jonasob/jwhois/issues/32 Signed-off-by: aszlig <aszlig@nix.build>
* profiles/workstation: Allow unraw via sysrqaszlig2022-05-141-0/+3
| | | | | | | | | | I just was forced to reboot my workstation while working on a program that sets the VT into raw mode but finding out that the unraw key now doesn't work anymore. This used to be the case but with the sysctl include that comes with systemd-coredump, the kernel.sysrq value defaults to only allowing sync (16). Signed-off-by: aszlig <aszlig@nix.build>
* workstation/redshift: Lower nightly brightnessaszlig2022-03-241-0/+1
| | | | | | | I've been testing 0.5 for weeks now and already got sufficiently used to it so that I'd become blind if it would be the default value (1.0). Signed-off-by: aszlig <aszlig@nix.build>
* aszlig/workstation: youtubeDL -> youtube-dldevhell2022-03-021-1/+1
|
* {aszlig,devhell}/profiles: Rename more packagesdevhell2022-03-021-1/+1
| | | | Even more packages are being renamed.
* treewide: Fix broken package symbolsProfpatsch2022-03-021-1/+1
| | | | | | | | Due to unnecessary renames in https://github.com/NixOS/nixpkgs/pull/161146 I replaced the packages with the ones the error messages mentioned, I have not checked whether they are actually a no-op replacement.
* treewide: reflect removal of pulseaudioLight aliassternenseemann2022-02-281-1/+1
| | | | | pulseaudioLight has been the same as pulseaudio for a while (apparently since 2018). The alias has finally been removed now.
* workstation: Switch Git diff viewer to deltaaszlig2021-07-221-0/+13
| | | | | | | | | | | | | | | | | | | I'm already using this config since a few months and since I'm slowly getting used to it, let's try to make it the default for my workstation profile. Unfortunately, libgit2 uses the Git configuration from /etc, but our configuration is directly patched into Git and not in /etc but in "${pkgs.git}/etc", so we need to patch libgit2 to use the right configuration file. Another goof is that we can't use ${pkgs.delta} directly in our Git configuration because it would introduce a circular dependency between Git itself and delta (which uses libgit2 which in turn refers to "${pkgs.git}/etc"), so for the time being I'm relying on $PATH for delta. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Patch XTerm to set $COLORTERMaszlig2021-07-091-0/+4
| | | | | | | | | | While ncurses already has support for detecting direct color terminals, a lot of applications out there do not yet query terminfo but instead rely on some shady COLORTERM environment variable. While I don't really like that approach, patching XTerm to set that variable currently is better than patching all the applications to query terminfo. Signed-off-by: aszlig <aszlig@nix.build>
* workstation: Advertise XTerm true color capabilityaszlig2021-07-091-1/+2
| | | | | | | | | | | | | | | | | | 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>
* workstation: Remove "git backport" aliasaszlig2021-07-091-6/+0
| | | | | | | | 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>
* workstation: Switch Git conflict style to diff3aszlig2021-07-091-1/+3
| | | | | | | | | | | | 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>
* modules/git: Switch to RFC-0042aszlig2021-07-091-1/+1
| | | | | | | | | | | | | | | | | 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>
* modules: Fix eval errors due to wrong test pathsaszlig2021-06-021-1/+3
| | | | | | | | | | | 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>
* modules: Properly link tests to machine configsaszlig2021-06-021-0/+2
| | | | | | | | 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>
* profiles/workstation: Add Flameshotaszlig2021-02-131-0/+1
| | | | | | | | | | | 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>
* modules/aszlig: Remove Taskwarrior moduleaszlig2020-12-231-1/+0
| | | | | | | | 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>
* workstation/packages: Remove NixOpsaszlig2020-12-041-1/+0
| | | | | | | | | | | | | | | | 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>
* modules: Rename enableFontDir to fontDir.enableaszlig2020-11-101-1/+1
| | | | | | | | | 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>
* pkgs/aszlig: Add Mutt configurationaszlig2020-08-081-1/+1
| | | | | | | | | | | | | | | | | | 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>
* pprofiles/workstation: Use true type VGA fontaszlig2020-08-081-5/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* workstation/packages: Add "entr"aszlig2020-07-281-0/+1
| | | | | | | | | | | | | 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>
* workstation: Disable pull.rebase in Git configaszlig2020-07-161-0/+1
| | | | | | | | | | | | | | | | | | | | 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>
* profiles/workstation: Revert replacing p7zipaszlig2020-06-151-1/+1
| | | | | | | | | | | | 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>
* pkgs/aszlig/xournal: Switch to xournal++aszlig2020-05-211-1/+1
| | | | | | | | | | | | | 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>
* profiles/workstation: Set XTerm colours to 256aszlig2020-05-071-0/+1
| | | | | | | | | | | 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>
* profiles/workstation: Replace p7zip with unaraszlig2020-05-061-1/+1
| | | | | | | | | | | | | | 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>
* treewide: Remove hardware.opengl.s3tcSupportdevhell2020-04-231-1/+0
| | | | | | | This option has been dropped upstream in 4732f59226a21b01d630c7ef4fb884bbfbe7dc83 Cc: @aszlig
* treewide: Switch to displayManager.defaultSessionaszlig2020-02-101-3/+1
| | | | | | | | | | | | | | 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
* profiles/workstation: Remove xpdfaszlig2019-12-081-1/+0
| | | | | | | | | | | | | | | | | | | 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>
* treewide: Remove all references to SLiMaszlig2019-12-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 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>
* profiles/workstation: Add wcc to packagesaszlig2019-10-131-0/+1
| | | | | | | | | | | | | | 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>
* pkgs/santander: Remove obsolete packageaszlig2019-09-231-1/+0
| | | | | | | 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>
* workstation: Fix latitude/longitude optionsaszlig2019-09-231-2/+3
| | | | | | | | | | | | | 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>
* profiles/workstation: Switch from Gajim to Psi 2aszlig2019-06-212-2/+6
| | | | | | | | | | | | | | | | | | | 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>
* profiles/workstation: Remove lastwatchaszlig2019-03-191-1/+0
| | | | | | | 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>
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-07-09 12:27:26 +0000