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.
view the rest of the comments
No, if it implements any standard file I/O, it'll work. Write to a fifo and then consume it with the other application. Or write into the fifo from another application and read it with the GUI app.
The point is that you can't "pipe GUI output to other command", the GUI would actually have to serialize things in a useful way and send to that fifo. Similarly you can't send stuff to it's stdin and expect it to do anything sane.
Further, since you can't seek() in a fifo, a lot of likely GUI applications involving files would break on trying to deal with a fifo. Also the typical GUI app on read doesn't assume a 'tail -f' like approach to arbitrary file inputs.
Yeah you can't run a one-line pipeline, but you can still pipe between applications. Just a little more asynchronously.