

Heho,
Just a guess. The tmux session may persist env. Thus nvim reads eg DISPLAY and thinks it must still be a wayland compositor.
Hope it helps


Heho,
Just a guess. The tmux session may persist env. Thus nvim reads eg DISPLAY and thinks it must still be a wayland compositor.
Hope it helps
I guess there are multiple working and proven ways. The above is the one which worked for me as a full time Principle in a 10000+ “shop” over years now. Whatever will work for you will be your preffered way.
Running my nix config incl. dot files on multiple OS from wsl and Mac for shell env and paths specific coding envs via devenv to nixos on my workstation and server.
I started with home manager on wsl till I got comfortable and switched to nix full time in the run. Was a chore at first. Now, i do not want any other environment for coding. It just works and can replicate and sync all working environments with ease!
Same story. Ssd of my machine for work crashed and after the replacement I was ready for work with everything customized and configured 30 minutes later.
A new node for my cluster arrives? 30 minutes later the new one is setup and integrated in my k8s home setup. Reusing complete profiles combined with files for hardware specifics.
I can even upgrades major versions fearlessly and had 0 problems the last years.