| Summary: | Autspawning terminal | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kcoreaddons | Reporter: | Lach Sławomir <slawek> |
| Component: | general | Assignee: | Michael Pyne <mpyne> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | wishlist | CC: | kdelibs-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| URL: | https://forum.kde.org/viewtopic.php?f=83&t=163751&sid=023b1d9adc315086d1d1219a25605ee8 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Lach Sławomir
2019-12-18 16:07:20 UTC
I forgot to add links: https://forum.kde.org/viewtopic.php?f=83&t=163751 https://sourceforge.net/projects/cli2gui/ There is a 'Run in Terminal' option for .desktop files. If users are expected to launch scripts outside of a terminal, they should provide such a desktop file. What about shell scripts/text-based installers. Problems is user can download text installers (why software vendors should select between GUI and CLI or order user to known, which installer to download? Qt doesn't provide GTK+ check_init functionality), which isn't prepared to run in GUI. Software vendors could prefer console mode, because it's always available - GUI could been disabled (in servers, for example). Of course, software vendors could provide solution by they own, but not better to deliver standard way. cli2gui-exec is program, which exec using parameters given in command line. This tool will spawn console, if needed. If cli2gui-exec tool will be accessible for software vendors, then script could have interpreter set like that: #!/usr/bin/env cli2gui-exec /bin/bash And that's all. |