How can I use this in nixos? #166
Replies: 13 comments 36 replies
-
|
Hi, thank you! It should be possible in theory, but I'm not sure how nix configs work as I'm kinda new to Linux as well and only (mostly) used Arch. If anyone knows how to re-configure this in nix, fill free to copy my dots to create a nix version! |
Beta Was this translation helpful? Give feedback.
-
|
(and to share the link into that discussion) |
Beta Was this translation helpful? Give feedback.
-
|
nixos is amazing, similar to flatpak in dependency management, additionally a similar project to flathub: https://mynixos.com/. I would suggest a simple HyDE.nix that installs/wraps all deps, then simply copy over the dotfiles same as arch. System configs like mkinitcpio are also done in nix files. Warning about home manager, it restricts access to the home folder. (Most people redirect their dotfiles anyway, I don't... Vanilla supreme) Avoid experimental features like flakes, version control won't be necessary for nixos users. Consult: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @kyn-0s1r15, I was able to do it with a flake. Basically, it's what you said: install Hyde-cli, then use Hyde-cli to restore the dotfiles. Here is my repo for the flake.. The Readme will guide you on how to set it up. |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on this - https://github.com/ashe/dotfiles/tree/theme-switching Note that due to the nature of my config its heavily specialised to my system. That said, if you look at Some things will need scripts to get around; others need some home-manager hackery. It's a slow process. Right now, GTK is the most annoying thing (maybe this is why hyprdots prefers dolphin over nautilus, food for thought 😛 ). I think it's because nautilus is on GTK 4 maybe? And I've only configured GTK 3? I have no clue. Will probably just move on to QT soon and then learn about Kvantum and how that works. Lots to do. |
Beta Was this translation helpful? Give feedback.
-
hey sorry I have not used NIX, but all the scripts I use here are very much kinda basic, so these scripts should work in NIX as well right?!?
Kvantum is completely svg file based engine, so its highly customizable, easy to manually modify from an existing theme but difficult to generate it on the fly! |
Beta Was this translation helpful? Give feedback.
-
Thank you so much, for your support! please refer theming.md for the config file structure. (its a bit outdated, but I'll update it when i get some time)
sounds great... once you configure one theme to work on your system, the others should be simple to implement, so no worries... Also let us know once you are able to get this working and I'll link your repo, so user who prefer NIX can use your version! |
Beta Was this translation helpful? Give feedback.
-
|
Current progress with rofi looks like this:
I have no idea what's going on honestly; I'm using your rofi config and even though the wallpaper is appearing the list box is not.. If I delete "inputbar" from the children of mainbox, or if set enabled to false for inputbar, then things start to work. Unsure if it's a bug or what. Little bit weird as it doesn't seem logical. No errors when running from the command line either. Style 2 functions a lot better thankfully! I'll stick with style 2 and crack on with waybar next. I've been waiting a long time to redo my horrific looking bar so looking forward to seeing what we can do! I am looking to implement rofi theme switching and making use of the import functionality. I'll essentially have all styles loaded in my nix config and then use a script to glue it together. I need at least 1 working style for that to happen though and it's low on the priority list so for now I'm just assuming 1 rofi config :)
Don't get your hopes up, I don't think I'll be able to 100% implement everythign your dotfiles implements. I love your theme switching for terminals and your rofi/waybar (and probably dunst) coordinated themes and want to take inspiration (read: steal 😛 ) them. I did actually implement the wallbash stuff as I didn't really understand the point; when I actually got to the part where my colourscheme can get set via the wallpaper I actually realised that's not quite what I'm looking for. Don't get me wrong, that's a cool feature, but my reasoning is that that's a lot of work for me to maintain. The nix way of doing things would be to do a lot of this work at compile time. I'm using your scripts where it's just doing some simple editing, but when the majority of the theming comes from stuff like wallbash then that's when it's less in the hands of my nix config. You could fix this by listing your wallpapers in nix, but I like the idea that I can just plop in whatever wallpapers I like. The magic is all in this file. You can see here that I've
None of this is drop-in so I'd hesitate to say someone can just copy what I've done. That said hopefully it's a good starting point for someone :) So, tl;dr, I'm not implementing everything and I'm sure someone will do a 100% faithful recreation of your dotfiles (and maybe they will find mine a good starting point?). I like the idea that I have lots of themes and that nix will check if I've missed any files when I try to regenerate my config, but the more of your stuff I implement the more I'm relying on bash and not nix. Thanks as always for your hard work :) if you know why that rofi thing might be an issue please let me know! |
Beta Was this translation helpful? Give feedback.
-
|
Which commit and lines concern HyprDots? |
Beta Was this translation helpful? Give feedback.
-
|
@bphd everything in that linked file on that branch is related to hyprdots. That's the starting point. Then you have the adjacent script directory, as well as all the bespoke methods for injecting themes into my config. Again, this is not a general thing, it's just how I've done it for my config. I don't have the know-how to do this in a way which satisfies everyone's configs especially when the home-manager modules are intentionally immutable. You need to essentially add an include that is not in your config, that you then generate separately using |
Beta Was this translation helpful? Give feedback.
-
|
@Ashe, sure it's okay for it not being a general thing, even if it's Ashe's HyperDots it's okay. I've just wanted to make sure to not apply things that really have nothing to do with the work you've did related to Prasan's HyperDots |
Beta Was this translation helpful? Give feedback.
-
oh strange, does it only happen with style_1? my wild guess would be the so, could you please try adjusting (reducing) this value (also try using px instead of %) to scale it for your monitor res...
Hahaa no worries... I didn't mean 100% feature parity, i was Just referring to wallpaper and theme switching.
Oof... Looks like I underestimated the work required to configure nix... But your config files looks good, so looking forward to see it working in your system :) |
Beta Was this translation helpful? Give feedback.
-
As I have learned myself, it's quite the undertaking. Initially, I started with your repo and started porting things, but have now switched over to starting from scratch and picking bit after bit and getting it to work. The other approach might work to, but this way I'm actually learning all about GTK and Qt theming, so that's a bonus for me. I'm sure there is a much easier and direct route to "just getting Hyprdots to work" on NixOS, it's just that I want to do things the NixOS/Home-Manager way, which is partly incompatible with... pretty much every other way. I have arrived at roughly the same setup that @Ashe also has - or at least that's what I'm planning, I'm not quite there yet. @Ashe if you'd like to chat about the porting and dynamic theme switching, I can be reached on Matrix (Cu3PO42@matrix.org) or Discord (@Cu3PO42). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the offer but my dotfiles are in a place I'm happy with; I have a way of switching my colourscheme, wallpaper and bar on the fly. It's not a full port but I'm also just busy with other things. My main objective was to be able to change my colourscheme without rebuilding my config and hyprdots already had collected a nice set of cohesive colourschemes and wallpapers. Thank you to everyone involved :) |
Beta Was this translation helpful? Give feedback.
-
|
Being happy with my dotfiles is definitely something I aspire to be some day, so I salute you! That being the case, I might yoink a few bits from your config should I get stuck. |
Beta Was this translation helpful? Give feedback.
-
|
What's the latest situation? Is the same for NixOS? |
Beta Was this translation helpful? Give feedback.
-
|
To my knowledge nothing has changed. Ashe has ported parts of the functionality to her dotfiles (which are linked above) and I am currently working on my own port. However, my work is still very much in progress and not yet public. I do, however, aim to produce NixOS/Home-Manager modules that you can just drop into your config. I'll post here once I have gotten to a state I like. |
Beta Was this translation helpful? Give feedback.
-
|
Hey all! I want to give a quick overview of my progarss towards replicating a similar feature set on my NixOS system with Home-Manager. First off, let me say that the amount of effort that must have gone into Hyprdots is quite astonishing and I do appreciate your work. I initiall thought I could get away with checking out the repo, applying a few patches and rewriting the installation scripts. The problem is that there's only one thing that Home-Manager dislikes more than state and that is state mixed with configuration. Core ApproachChromaI rely on an approach similar to, but still somewhat different from, Ashe's. The core of my efforts is my new theming module that I've dubbed Chroma. You can find it in copper-chroma.nix. It exposes a theming system that other apps and frameworks can be plugged into. Integrations for supported applications are then defined in the copper-chroma folder. Theme definitions are not distributed among the various application configs, but centralized in the themes directory. From this definition, I build one folder per theme, containing all relevant files and settings. For configurations that support includes, I only include the theme config, for tools whose configs do not support includes, I template the whole configuration. All tools are configured to read configs from SwimI have also built wallpaper switching from the ground-up as my swim module. Swim can hook into Chroma to offer a different set of wallpapers per theme. Due to the modularity of Chroma, it needs no special knowledge of Swim and the only Chroma-specific code for Swim is remembering the last-active wallpaper for each theme. Neither of the above know anything about Rofi or the thumbnails it needs. Further DifferencesWherever possible, I strive to isolate features from one another as much as possible. You can pick and choose which parts of Hyprdots you want to activate, by activating my corresponding features. I have tried to keep any large assets out of my main repository, that means I install all themes from a package: preferably from the standard sources, though I have also packaged themes that weren't already available. Luckily, most themes are already packaged in nixpkgs, so I didn't need to do significant work for them. One that was not already available is the SDDM theme, which I have packaged in My Hyprland initialization is quite different from upstream. Instead of launching dunst, waybar, etc. as part of my Hyprland configuration, I manage all of these via systemd user units. Also, the Feature supportAs of now, this is an incomplete port/rewrite, and it will never be complete in the sense that there's some features I don't plan to port.
Among the things I don't plan to support for the forseeable future is:
Thare are also some things, which I plan that are not yet in Hyprdots:
AdvantagesThere are two main advantages to my approach: it is easily extensible, i.e. someone could easily maintain theming for their own set of applications without needing to maintain a fork and someone else could easily have their own local themes. It is also easier to cross-reference theme settings without complicated scripts. For example, I can easily set the Qt font based on the same value as the Gtk font without any need to parse configuration files, since everything is available in Nix. Usage under non-NixOSFurther, the majority of my configuration work is specific to Home-Manager and can be used on non-NixOS Linux distributions that uses systemd. This should get you a majority of the way, even if Hyprdots doesn't dirctly support your distribution of choice. You'll loose out on anything configured in the NixOS module.
Future OutlookI'm not nearly done yet. I'd like to clean up my configuration some more, verify that everything works as intended, and write documenation. When I'm done with all that, I will probably make some more adjustments so that this is not just Hyprdots but for Nix, but rather a mix of Hyprdots and my own preferences. Of those tools and configurations that I ultimately keep, I'd like to rewrite their config generation scripts. While I have kept them mostly as is for now, a lot of the work that happens in QuestionsFinally, I'd also like to use this opportunity to ask some questions, which I haven't yet achieved clarity on. I'm hoping you can provide your insight, @prasanthrangan:
|
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone! I'd like to give you another update on my efforts. Not too much has changed over the last weeks, as I actually took some vacation time. And though I haven't pushed anything, I have, for example, gotten libadwaita theming to work consistently and made some configuration more flexible (e.g. Qt now always has the same font as GTK). None of that is published yet, but it should be very soon. Unfortunately, I have come to realize that while Hyprdots is great and a tremendous effort, for a variety of reasons, I will not pursue a straight up port of Hyprdots to NixOS/Home-Manager anymore.
I want to truly thank everyone involved with the project for their work and wish you the best with the continued effort. It has gotten me off the ground and inspired many design decisions I have made, and some parts of Hyprdots will continue on in my own configuration. For anyone else on NixOS/Home-Manager, you are welcome to look at my configuration and keep an eye out for future updates. I aim to make it easy to include in other Flakes, but I do not yet have documentation for all of the new theming modules. And again, it's not a complete port of Hyprdots, but rather my own configuration that uses some parts of Hyprdots. |
Beta Was this translation helpful? Give feedback.
-
|
All of the updates I talked about are now available on my repo! I've also made some minor adjustments/fixes to my port of Hyprdots functionality. However, this is likely the last of Hyprdots-related updates for now :-( |
Beta Was this translation helpful? Give feedback.
-
|
@Cu3PO42 Did you remove the chroma repo? I don't seem to able to access it. I'm in the exact same situation as you and seeing the same issues with nixifying, so even getting to look at your conf as a reference would be worth a lot. I might even be able to do a PR on some stuff that you are not prioritizing - like Spotify themeing :) |
Beta Was this translation helpful? Give feedback.
-
|
@maxbol Not as far as I can tell. The links above still work for me, even in a private window. However, the linked branch is now out-of-date. I'd recommend you look at I'm generally happy to accept contributions, though Spotify in particular is not something I'm using, so I'm not sure about having that upstream. That said, Chroma is designed to be fully extensible from your end without a fork, so that shouldn't pose any problem. Feel free to shoot me a message about features you're missing and we can discuss how to best add them. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, seems like there was some issue with the GH mobile app. Working as expected on desktop :) |
Beta Was this translation helpful? Give feedback.
-
|
Headed here to see progress as I hadn't the time to port it myself and @Cu3PO42 has made something really good to think the project "statelessly" or idk how to name that, but it has become such hydra that I truly don't know how to handle it, worse, now it's semi-abandoned as it strongly derived and integrated own dotfiles to become something totally different. Though the theming project it had gave birth to is really promising, it has to find it's public now. @Ashe has (I think) not much changed since and is like a subset integrated into dotfiles without a clear way of what and how to take it to implement into self systems. So so far this theme still is a dream for me ahah |
Beta Was this translation helpful? Give feedback.
-
|
My dotfiles aren't abandoned at all. But I have merged Chroma into a new branch, thus new stuff is happening there rather than the branch linked above. It's called |
Beta Was this translation helpful? Give feedback.
-
|
I talk about "semi-abandoned" talking about the more "authentic" port made before |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone tried simply modifying the file paths in all the scripts and configs that reference files that don't exist in NixOS (e.g. anything in |
Beta Was this translation helpful? Give feedback.
-
|
Honestly, having come this far, I have some understanding of how Hyprdots works overall. At this point it would be easier to just take what I want and go my own way. But I've already come this far and now I'm just curious to see what will happen if I try running hyprdots as is on NixOS with my changes. I just wanna see if this thing blows up or ends up working 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
@kik4444 If you managed to do it on Nixos I'll be trying nix on one of my machine. I guess it would be cool if we have a port Hyprdots for NixOS, if possible. Thanks in advance! |
Beta Was this translation helpful? Give feedback.
-
|
It's still the nix language at the end of the day so it's the same. Though the way you structure the config between a full system and home-manager standalone will likely be different. |
Beta Was this translation helpful? Give feedback.
-
|
Here's my experience with the last patches I made #1152 |
Beta Was this translation helpful? Give feedback.
-
|
Nix Is thought at core to be break immune, little bit like Fedora silverblue. Would be utterly funny that it doesn't survive such operations. As long as you don't touch the read only mounts, the system should be able to reproduce itself to identical state. At least it's how it's sold and why much people use it Though idk the logic behind implementing inside and outside of home, maybe @prasanthrangan should know. But afaik, home conf have priority over any other and /usr ones tend to be the default one, multi user one, root ones. It's generally way more reliable to apply those in multiple place in case something doesn't care about home configuration. More than that idk, have to check on a software basis manual to know when and where and if they take into account home configurations. Afaik you can even generate a VM machine upon recompiling of the OS to test on a safe environment that still is pretty much a 1:1 to yours to be sure about compatibility (considering you don't tweak outside of NixOS configurations files) @kRHYME7 You can install HM and NixOS aswell on any other OSes, it's a package manager first and foremost. Like actually I use Nix package manager on Guix when I'm too bored of porting something, because even if Guix follows the Nix logic it's like really more complicated to port things. For example for HyprDots, I'd have to find how to convert SystemD hooks to SheperD ones. Though SheperD is really more close to POSIX logic than SystemD |
Beta Was this translation helpful? Give feedback.
-
|
Hello let's assume we can fork and maintain this project with Home Manager( Will try to use it again in arch). Is this compatible with (lesser adjustments) for the whole nix OS? Also having it in HM, by theory we can install this easily in any distro including debian base,right?. |
Beta Was this translation helpful? Give feedback.
-
|
Can you use this in arco Linux? |
Beta Was this translation helpful? Give feedback.
-
|
It should work on any distro that uses |
Beta Was this translation helpful? Give feedback.
-
|
Can't I download all files that use git I have bad network so when I tried installing I had errors and sometimes not because of network I didn't know what was even wrong can you help me figure it out? I can give you my telegram or something please sir |
Beta Was this translation helpful? Give feedback.
-
|
We got a Discord channel. Check it out in README. Here's how we can install it
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry to ask so many questions but what do you mean by SINGLE and also git for me don't work mostly |
Beta Was this translation helpful? Give feedback.
-
|
My bad I meant Single theme While in installation it will ask you this. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I have just succeeded in making hyprdots work in nixos. Here's my flake if you are interested. |
Beta Was this translation helpful? Give feedback.
-
|
Guix here |
Beta Was this translation helpful? Give feedback.
-
|
I'm working on the home-manager nixos implementation here @ hyprdots-nix. currently supports being run as a vm for easier development decided to support both the standard @kRHYME7 's hyde-cli installation and home-manager as there's some caveats around the proper nix way to do things. hyde-cli method will be setup soon. for now @sandeng1440 has a good way. |
Beta Was this translation helpful? Give feedback.
-
I just recently discovered hyprland, and this excellent repository. Since I'm a novice in this area, a quick question: is it possible to use this repository on nixos?
Beta Was this translation helpful? Give feedback.
All reactions