Earlier quoted context omitted.
I didn't even know that was possible but I think it would be the perfect solution, as long as it ran efficiently and managing the hotkeys between both sessions wasn't a problem. I wonder how that would work if you used the same configs. If it were possible to pull off, that would be the perfect combo: - A dedicated 1920x1080 recording zone, using Hyrpland's config file to automatically resize and position this Hyprla…
I've only used it for testing/debugging so I didn't need any of that capability. I'm not sure why they recommend avoiding exec in the config. Since it would still be under the same user session, dbus things could get wonky. Nested hyprland will automatically create/use ~/.config/hypr/hyprlandd.conf and you'll def want to have unique keybinds. If you haven't gone too crazy with keybinds, just changing the main mod key…
It's probably going to get complicated though due to wanting to run waybar, walker, wallpaper, etc. in the nested session but if you do anything that's going to modify its state in that session is also going to affect the outer one since only 1 process runs for those tools.
It's almost like you need a separate copy for everything that runs in exec but with a different process name too.