view the rest of the comments
Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
Tangential. I tried everything to replicate the basic function of an app launcher in a terminal - i.e. launch a GUI app while leaving the terminal unaffected and have the app survive without spontaneous combustion at some random point later - before finally giving up. Yes, background process. Yes,
disown. Yes, redirect all output to null. Yes,nohup. Yes, every combination of the above. Nothing really worked. So I now have a mystical reverence for the people who write app launchers.In X11 you can just use 'exec app-name' and it will replace the terminal window with the app. In Wayland, I got it to work with this:
Without the 'sleep 1', it exits the terminal too quickly for the app to launch, at least when I tried it.
*Edit: In order for it to work as a script, you still need to type exec first. Or, in my case, I aliased "open-app" to "exec open-app".