2026-01-23 -> 2026-02-20 #72
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The main motivation for this bump was to fix a bug with GNOME Calendar that was using the wrong timezone for an event's time slot (see: https://gitlab.gnome.org/GNOME/gnome-calendar/-/issues/1456). During the bump, I discovered that `dms-shell` was now available on Nixpkgs, and that it was fairly up-to-date. As a result, I have decided to remove it's flake input and use what is provided on Nixpkgs. Alongside it I removed the Quickshell package, as once again I saw that Nixpkgs had the up-to-date version, and I hated having to constantly rebuild it every time I bumped the input. The quickshell derivation would usually always take the longest to build, and it would severely slow down my rebuild time.
I noted back in 8bfd774 that my neovim colors seemed to be broken. It turns out that this update brought in something that I didn't quite realize, something that even the treesitter warning in neovim did not sufficiently warn about. It seems that nvim-treesitter developers have begun a full, backwards-incompatible rewrite of the plugin. This changed a huge variety of things, and one of the many was that highlighting, amongst other things, was not configured via `require("nvim-treesitter").setup({})`. This meant that my old configuration for it was silently failing for a while before I realized. After enabling highlighting (via an operation that might not necessarily be safe..), my colors have returned to normal.
The `redhat.java` extension made a change to start bundling JREs for platforms that they support. Since I have been grabbing the extension by setting it's `arch`, it would provide me with a version of the extension that contained a bundled JRE. The way to avoid this was to force the extension to use my own defined version of Java, by setting `java.jdt.ls.java.home` in the VSCode settings. This is an annoying fix that forces me to declare it in my configuration. Another solution was to drop the `arch` entirely, which would fallback to a "universal" extension variant. This universal variant did not bundle a JRE and relied on `JDK_HOME`, `JAVA_HOME`, or `PATH` to find a suitable Java installation. This meant that I did not need to tweak VSCode settings, and the extension would rely on the version of Java presented in any development shells. Funny enough, the Nixpkgs variant _is_ the universal variant. I'm not sure if that was an intentional decision, but I'm rather grateful.
A recent change to NixOS added hardening to the `wpa_supplicant` daemon, which caused me to be unable to connect to the school wifi. Thankfully the fix itself is relatively simple, and since I prefer managing these certificates imperatively, I've gone ahead and enabled persistence for this directory.
Prior to this I was indiscriminantly enabling treesitter on everything that would invoke the 'FileType' autocommand. Turns out that is not a good idea. Instead, I first check if the language is supported, then activate treesitter for it.
The former is a deprecated alias to `pkgs.xset` on a newer revision of Nixpkgs, so let's just move it ahead now. Side note: why is Nixpkgs been moving packages from namespaces like `pkgs.xorg` into the toplevel? I kind of liked it being organized the previous way..
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello there and happy new year! A new staging cycle has started up. The last cycle was 2025-12-25 -> 2026-01-08.
This cycle has had its duration extended to 4 weeks to accommodate for the fact that I am currently busy with school. No particular targets are intended to be achieved, just routine maintenance and fixes to keep my system chugging along.
Breaking Changes
TODO
New Features
redhat.javaextension (38c29ea)/etc/wpa_supplicantfor network certificates (cce7433)Fixes
xorg.xset->xset(37d5620)