Hey devs,
I am using flex-launcher in a tiny setup with SwayWM, configured to maximize all windows, with a few programs that usually runs fine, but I am sometimes curious about what some of them do during startup. If a program errors out or waits for something else to respond, flex-launcher just exists and I am left with a blank background until the program eventually starts or I give up.
I can see the stderr/stdout by adding a terminal program to the execution, like foot some program, but this creates a new window that could potentially mess up the window layout.
Do any of you know of a way to print/log output during application startup, or do you solve this problem another way .... if you see the problem at all?
Hey devs,
I am using flex-launcher in a tiny setup with SwayWM, configured to maximize all windows, with a few programs that usually runs fine, but I am sometimes curious about what some of them do during startup. If a program errors out or waits for something else to respond, flex-launcher just exists and I am left with a blank background until the program eventually starts or I give up.
I can see the stderr/stdout by adding a terminal program to the execution, like
foot some program, but this creates a new window that could potentially mess up the window layout.Do any of you know of a way to print/log output during application startup, or do you solve this problem another way .... if you see the problem at all?