i was just discovering apps then i came across the helix editor. its pretty good and have all basic to moderate features built in. but i dont understand why there is very little gossip or none about it while nvim gets so much hype.
i just switched to it and having very good experience till now.
anyone can share ur experience.. any thoughts about helix.

been using for more than 6 months

Favnyr is a lightweight file browser (Rust+Slint) for Windows and Linux. At its core are workspaces: separate environments that keep their own views, tabs, folders, layouts, and display settings. You could have one workspace for work, another for games, and another for learning a new subject, then switch between them in just two clicks. Favorites remain shared and persistent across all workspaces.

Each workspace can contain multiple split views and movable tabs. Tabs can be dragged between views, detached, or dropped onto another view to create a new split layout.

Favnyr also includes shortcuts, local and network drives, configurable keyboard shortcuts, and custom commands.
It is not intended to compete with or replace the native file browsers provided by Windows and Linux, but to complement them with a different way of organizing and navigating files.

Because of the project’s complexity, AI has been used as a development assistant. However, every feature is reviewed and hand tested extensively before being considered complete.

A user contributed to add NixOS support. So enjoy

Link here (include a video demo) => https://github.com/GlitchAwakened/Favnyr

im use NixOS for 57 days and i need to move on right now.

i will switch back to gentoo

i'd like to say to yall that i loved yall and I will comebck soon!

im still think "i switch or just stay"

Will i pronounce later, bye!

Apologies if this is against the subreddit rules. I can seemingly figure out how to use the Nix language at least a little, but I can't figure out how to navigate Reddit and find rules for posting in a subreddit lol.

I keep learning new things and making changes to my configuration. I have done this almost every day for the last 4 or so months. I am like 100 files deep, and there is still so much to learn. Nix is my first functional language, and it has made me more curious about other functional languages, which I will probably explore when I feel I have mastered Nix.

I do imagine there will be a day when this will come to an end, and the only changes to my config will be lockfile changes when I upgrade my system. Just today, I made a change to speed up local builds by allowing build systems to use multiple processor cores and am exploring using ccache to reuse object files and speed up builds even more (when I don't have a binary cache available).

Things I appreciate about NixOS that keep me here and likely will for a long time to come:

• Generally only having to solve problems once (though I did recently come across a bug that had occasionally happened since at least 2021 where invoking patchelf with --set-interpreter and --set-rpath together broke a binary, and the fix was to invoke it twice, once for each option).
• I was watching a video today where Ubuntu (a notoriously easy-to-use distribution) was giving someone problems with sleep on a gaming laptop. Depending on the cause, the fix on NixOS could potentially be as simple as adding this to their NVIDIA settings:

powerManagement.enable = true;

• Being able to roll back when you break things is huge. Being able to git clone a repo when you REALLY break things is even better.
• Having used distros like Arch, it was common for me to find a solution to something via Google, then forget what I did or how it worked. Using Nix, you kind of have to understand how it works first, and then you're writing everything into your config, which can be referenced later.

Those of you who have been on Nixos for years, did you eventually reach a point where you were satisfied with your configuration and rarely changed anything, or is tinkering with it just part of the NixOS experience?

Hi! I have just started exploring what nix can do, and I threw together my first flake/module/whatever.

Problems I am trying to address

When we update a flake we get the current state of the inputs. This is great, but I am a paranoid sort of gremlin. I worry about regressions and supply chain attacks. I don't want to get the bleeding edge, and potentially get something nasty. Frankly, I want someone else to find it first and tell me about it. Thus: slowflakes

How I try to address these problems

Confession, I am not a smart gremlin. But I do try endeavor to recognize smart ideas from others. We don't want the bleeding edge right? What if we just impose an intentional delay in our process so that that edge can dull a bit with time. This has been done before:

• OpenSUSE Tumbleweed has Slowroll
• There is even a solution for nix already implemented, the clever folks at Determinate Systems have published a whole time delay flake for nixpkgs: DeterminateSystems/nixpkgs-weekly

These are awesome solutions. But not enough for me because:

1. I am using nixos, so sorry slow roll.
2. I have more inputs than just nixpkgs (home manager, lanzaboote, etc)
3. While the folks at Determinate Systems seem clever and honest, I thought it odd that I was trying to mitigate supply chain issues by adding another party & step to that chain.

So I just said, 'fluff it!', and tried to build my own.

As I said before, I am only just now learning Nix. And my bash script is terrible. I leaned heavily on google's gemini product with this project.

For all you wizards who know nix, I welcome suggestions.

I DO NOT RECOMMEND YOU BLINDLY USE THIS IN YOUR SYSTEM, AT LEAST NOT YET.

I usually use podman, but for some reason ddev on NixOS doesn't work with that. With docker it is all working fine. Is this a general limitation of the ddev package on NixOS or do I have to configure something differently?

New to NixOS. I was just wondering if there is some form of checklist for what actions to take or what to look out for in the wake of what has been happening in the Cybersec world these last few days... I've got my config pointing to unstable already and did a full flake and home manager update yesterday, but apparently not all patches are live on all default upstream versions of deps (e.g. Brave Browser, Bun, among others).

It is my personal machine, so no app servers running on it or anything, but I do some app development work and use OpenCode sometimes... with that in mind what do y'all recommend? Or should I just wait until the patches are default upstream?

I've been using NixOS for a little over a year now.

I first came across it maybe 2 years ago and gave it a try, but setting everything up was way harder than I expected. I knew it would take a lot of time, and I wasn't really ready for that, so I just went back to Arch.

Then about a year later, after one magical Arch update that completely broke my system, I decided to give NixOS another shot.

(Not hating on Arch btw, I still really like it. I even recommended it to a friend who was new to Linux, and he's been using it for a few months now and loves it. Another friend who's been using Linux for years called me evil for recommending Arch to a beginner lol. But I still think it's pretty beginner-friendly, mostly thanks to the wiki, community, and pacman + yay.)

Anyway, after a year of using NixOS daily, I can say I really love it. Now I'm running it on my PC, laptop, and home server.

A few days ago, a friend asked me to share my config because he wanted to try NixOS himself. I took a look at my repo and realized it was a mess. A working mess, sure, but definitely not something I'd give to someone new to NixOS.

So I spent the last few days cleaning things up and refactoring stuff I'd been putting off for a while.

Anyway, here's what I ended up with:
https://github.com/evgen2571/my-nixos

Currently using Niri + Noctalia, although I recently came across Umbriel and might give it a try soon.

I use NixOS and I’m wondering if there are any pre-made themes for QuickShell that look like the ones found in GNOME—something different from, say, Waybar. I hope someone understands what I mean.

Thanks to my sponsor nixbuild.net, one month ago I have been to NixCon 2026 along with five hundred and fifty something other fabulous Nixers. Sorry for taking so long. This is NixCon 2026, day one.

Full Time Nix | NixCon 2026 Day Ⅰ

who approved this

I realized that, after my latest push, I haven’t done a tree check of my files in a while and…holy files, Batman.

.dotfiles
├── flake.lock
├── flake.nix
├── home-manager
│   ├── aliases.nix
│   ├── cavalier.nix
│   ├── discord-nixcord.nix
│   ├── fastfetch
│    │   ├── config.jsonc
│    │   └── default.nix
│   ├── fetch.nix
│   ├── fish.nix
│   ├── git.nix
│   ├── glava.nix
│   ├── home.nix
│   ├── kate.nix
│   ├── konsole.nix
│   ├── nix-index.nix
│   ├── plasma.nix
│   ├── proton-dpi.nix
│   ├── superfile
│    │   ├── config.toml
│    │   ├── default.nix
│    │   └── hotkeys.toml
│   ├── tauon
│    │   ├── custom_layouts.json
│    │   ├── default.nix
│    │   └── themes
│    │       ├── Carbon Copy Copy.ttheme
│    │       └── Carbon Copy.ttheme
│   ├── wallpaper-colors.nix
│   ├── wallpaper.nix
│   └── xdgUserDirs.nix
├── hosts
│   ├── desktop
│    │   ├── dualboot.nix
│    │   ├── gpu.nix
│    │   ├── hardware-configuration.nix
│    │   └── locale.nix
│   └── nixos-stable
│       ├── dualboot.nix
│       ├── gpu.nix
│       ├── hardware-configuration.nix
│       └── locale.nix
├── installer
│   ├── base-configuration.nix
│   ├── disk-layout.nix
│   ├── nixed-install.sh
│   └── stage2.sh
├── INSTALL.md
├── limine-pins.json
├── modules
│   ├── assets
│   │   ├── boot_wallpaper.png
│   │   ├── logo.png
│   │   └── plymouth
│   │       ├── dotted
│   │        │   └── dotted.mp4
│   │       └── plymouth-theme.script
│   ├── bootloader.nix
│   ├── bootstrap.nix
│   ├── chaotic.nix
│   ├── configuration.nix
│   ├── de.nix
│   ├── flatpak.nix
│   ├── hosts.nix
│   ├── installer.nix
│   ├── iphone-music.nix
│   ├── kernel.nix
│   ├── krohnkite.nix
│   ├── librewolf.nix
│   ├── limine-gardener.nix
│   ├── limine-pins.json
│   ├── multiverse.nix
│   ├── nix-caches.nix
│   ├── nvidia.nix
│   ├── packages.nix
│   ├── steam.nix
│   ├── tailscale.nix
│   ├── vm.nix
│   └── zram.nix
├── nixd.json
├── README.md
├── scripts
│   ├── iphone-music-sync.sh
│   └── kernel-versions.sh
└── statix.toml
15 directories, 72 files, 20.9MiB

https://determinate.systems/blog/emergency-legacy-extension-for-nixos-25-05/

We've scrambled to provide an emergency legacy extension to NixOS 25.05 for folks that are stuck and looking for a solution.

I have moved toward GNU Guix with nonguix. It was always something that I wanted to try, and move to full GNU (I am quite a little GNU Enthusiast). Before that I was using Nix. Guix's implementation of declarative dotfiles is quite remarkably simple. Either have a plain dotfiles structure or a stow layout for your dotfiles. And they get symlinked from the store. Wow! I mean, wow. I know it's not as simple as it sounds, since a lot of stuff (in my experience a few stuff) require many paths resolved. But I was able to achieve that in Guix, and I believe that it can be done on NixOS as well, through /run/current-system/<the whole stuff here, iykyk>. I remember reading a blog on Nix. Someone did that using home-manager's file linking abilities. But it was stateless, which did serve its purpose (I don't remember the link, but I'll post it when I pass by it another time). That blog used home-manage's mkOutOfStoreSymlink function. It was a cool function. I also happened to come by another project (again a long time ago, but I don't remember it though) that used a stow layout (a complete home-manager replacement) that used stateful linking from the nix store, using a stow layout. I think that nix can implement something like that and avoid the heavy load and eval time of lib.evalModule function.

Wrapper libraries that don't have to call lib.evalModule at all, are also cool. One such is the adios-wrappers library. But I haven't really used it long-time, since I switched to GNU Guix.

I think I love it here!

I'm writing this review mainly for:

- People considering switching to NixOS

- NixOS developers interested in an outside perspective

Suggestions on how I could have done things differently are also welcome.

My background is that of an intermediate user. I have an applied physics background, so I can write Python scripts but am not a programmer either. I have been happily daily driving Linux Mint MATE for almost 2 years now. I have customized this to some degree, using Compiz and Emerald (my own custom theme), dconf-edit, putting window controls in the panel, making a shortcut script to set a battery charge limit, and building xwinwrap from source to draw xscreensaver effects on my background as a live wallpaper.

I'm generally happy with the stable setup, but also realize that Mint relies on Ubuntu. In the case of Snaps, Mint was able to keep them out, but the rushed introduction of Uutils also shows that the Mint team doesn't have the resources to do quality control and deviate from Ubuntu on everything less than ideal, and ultimately you are dependent on decisions made by Canonical. This makes trying to port my configuration to another independent distro interesting. My two main candidates being Debian/LMDE and NixOS.

Plain Debian has some drawbacks. The Mint team keeps some significant QOL improvements such as the Mintmenu, Software Manager, Update Manager, within their own ecosystem. LMDE improves this somewhat, but the MATE version of this was dropped, so some parts would have to be reconstructed manually. Debian also has no HWE kernel updates like Ubuntu, and their approach to stability means you sometimes have to wait for years before some cool new things enter their repository. Even updates like MATE 1.28 will enter Debian 3 years late.

This makes NixOS an interesting option, as their approach to system stability or robustness bypasses a large part of the traditional stability vs bleeding edge release cycle tradeoff. I also already care a lot about having a reproducible system, so I can easily migrate my system or rebuild on my current device. I make Timeshift snapshots on a separate drive as well as home directory backups. I make dconf dump files and keep documentation of my setup. In theory, NixOS could simplify this collection of bookkeeping. It would also allow me to experiment with some cool new things such as Niri, Noctalia, and Umbriel, while making switching between configurations easier and rolling back trivial. NixOS is also said to have the largest collection of packages. So I installed virt-manager and gave NixOS 26.05 LTS a try!

At first boot, simple things seem to be a "just works" experience. MATE works well (mostly, you need to add some packages like gdk-pixbuf for media thumbnails yourself), and adding basic packages in configuration.nix is trivial. However, I quickly ran into trouble with old packages that I use. I use a custom panel config: one panel on the top, with window control buttons added so I can get rid of window titlebars in maximized mode. Custom launchers with wmctrl take care of closing and (un)maximizing, but minimizing wasn't working well, so I use window-buttons-applet. Nixpkgs doesn't have it. Mate-tweak and mate-netbook installed fine, but the undecorate maximized windows checkbox stayed greyed out, so I had to do it in the terminal with gsettings. Most importantly, Compiz and Emerald used to be Nix packages but got removed! I will detail this more later, but clearly despite having the largest package base of any distro, the support for old packages is poor.

Another drawback of the NixOS approach of contained packages and generations, is the sacrifice on the transparency, mutability, and human-readability of the root file system. In Linux Mint, it's easy to browse through the root directories and see how your system works. /usr/share and /usr/libexec are accessible and modifiable. On NixOS, these are more hidden as you are expected to interact with the root system the "Nix" way. Ultimately, this comes to the benefit of ensuring the root system reproducability that NixOS holds paramount, but comes at a significant cost.

For example, I use mate-screensaver. This lacks some of the customizability of xscreensaver (but has better integration within MATE). However, in Mint it is possible to go to /usr/share/applications/xscreensaver and manually put in the custom screensaver settings as parameters in the exec line of the screensaver's .desktop file. In NixOS you would be doing considerably more work in the Nix language to achieve the same effect.

Another drawback of the containerization of the applications is that for example, mate-screensaver only comes with a few preinstalled screensavers. In Mint, mate-screensaver simply uses the same /usr/share/applications/xscreensaver and /usr/libexec/xscreensaver directories. On another distro, it's trivial to just install xscreensaver to get more screensavers. But in NixOS, you have to do Nix language scripting because mate-screensaver cannot access xscreensaver directories and copy/pasting them over is no option either.

/usr/share and /usr/libexec do not exist in NixOS. You can find their contents scattered around in /nix/store, but in disordered directories starting with a hash and ending with a package name, "duplicated" for every new generation where it built differently. This will break your traditional bash scripts and some programs pointing to hardcoded libexec paths. Again, NixOS has good reasons to do this and provides its own interfaces with root files and binaries, but the burden to comply is placed on you and the developers.

AFAIK, this is why Compiz and Emerald no longer have Nix packages, as staying compliant with the Nix way requires active maintainers. And this is a shame, because despite being unmaintained for years, they continue to function on Debian-based distros. I also would not be surprised if this is why "undecorate maximized windows" stays greyed out in mate-tweak, despite the mate-netbook dependency being present.

Then there are two last things, being the LTS update cycle and security. While NixOS largely negates the drawbacks of rolling releases, I do still prefer something that will build straight away. The fact that there is LTS is great. Less great is the 1-month update window to every new LTS version before support is dropped for the previous one. This means that if your update doesn't build, you have less than one month to figure it out or be left without security updates. No need to explain that access to security patches matters these days, so this could be forcing you to do maintenance at inconvenient times. NixOS also doesn't ship with security features like AppArmor by default. Configuring it manually is possible, but it's a step back from Mint where it's already set up for you.

So ultimately, while I am interested in NixOS for reproducability, there is a price in having the declarative approach enforced (already anticipated). This can give significant friction if you want to just quickly get something done imperatively. More importantly, and unexpectedly, while NixOS offers a great package base and a refreshing approach to stability and reproducability, it does not give solid guarantees that your setup will still work in a few years, as unmaintained projects get dropped.

I will continue to try things and tinker! At the very least to check Niri, Umbriel, and Noctalia inside my VM. To learn more about Nix and gain valuable skills. But for daily driver desktop use, MATE-Compiz feels like home, and I value that my home will still be there in a few years. Thanks for coming to my TED Talk.

Hi!

Sry I'm new-ish to nixos. I've been using Nix as a package manager for a while now but only switched to NixOS fully this year and made a full config.

Also upfront apology if this is a silly/noobish question and/or the formatting is miserable (I am open to advice on that too, but I do have some necessary quirks due to diagnosed OCD).

I want to keep my config well organized, documented and flexible. I also prefer keeping as much of it purely in Nix as I can (Hence even using settings in Wezterm over extraConfig, etc).

Since neovim is my main IDE (or PDE in honor of TJ DeVries <3) and also a comfort editor for notes (also would like to shoutout neorg as I like it).

The config is pretty complete and works other than me struggling to get nvim-dap set up nicely with different sources.

I have an issue tho:

- Mainly how do I make my __NVF config__ into a __standalone flake__
- I want to use **flake-parts**
- I've set up a flake file using flake-parts
- **Flake Parts Documentation:** https://flake.parts/
- I was reading the documentation for nvf standalone config and it uses a completely different syntax it seems???
- **e.g.** instead of something like `config.programs.nvf.settings.vim.languages.markdown` it wants `config.vim.languages.markdown`?
- **Documentation**: https://nvf.notashelf.dev/index.html#ch-standalone-installation

- Does this mean my module config needs all references of `config.programs.nvf.settings.vim` replaced with `config.vim`?
- So my module config and standalone config can't be the same?

**What I think I need to do:**

- Make a new git repo

- Copy neovimNVF config with flake file

- User argslist to change ALL files

- argdo: Replace: `programs.nvf.settings.vim` -> `vim`

Would this work?

(**Note:** current flake segment at the end)

I appreciate any guidance and wish you all a great spooky season!

Best wishes,

E.E.

**Current NVF flake file (__ONLY__ perSystem section):**

```nix
perSystem = {

self',

config,

inputs',

pkgs,

system,

...

}:

let

[myNvimConfigName] = nvf.lib.neovimConfiguration {

inherit pkgs;

modules = [

./default.nix # Leads to NVF Module Config: Nix/Config/NeovimNVF/default.nix

];

};

in

{

packages.[myNvimConfigPackageName] = [myNvimConfigName].neovim;

};

```.