https://bugs.kde.org/show_bug.cgi?id=442740
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |usability
Component|general |general
Summary|Automatically detect app |Existing method to make a
|type and run in console |script file open in an
|window, if needed and user |interactive terminal is
|agree. |rather cumbersome
Version|unspecified |5.86.0
Assignee|fa...@kde.org |kio-bugs-n...@kde.org
Ever confirmed|0 |1
Status|NEEDSINFO |CONFIRMED
Resolution|WAITINGFORINFO |---
Product|frameworks-kded |frameworks-kio
Severity|wishlist |normal
--- Comment #8 from Nate Graham <n...@kde.org> ---
OKay, so here's the thing: we already have this ability: create a .desktop file
that executes the script, and enable the "open in terminal" option, and then
launch the .desktop file rather than the script However I can understand that
this would be fairly cumbersome, since it means you have two files to keep
track of and distribute, rather than one.
I can see a few potential options for how we could improve this situation:
1. Always ask the user whether they want the script executed silently, or run
in an interactive terminal. This would be helpful, but maybe annoying too.
2. Always open script files in an interactive terminal by default. This would
have the potential to break existing scrips files written with the expectation
of launching silently, though.
3. Add support for a developer-specified piece of metadata added as a comment
into the script file that would signal to the system that the script file wants
to be launched in an interactive terminal. However this pretty much duplicates
the existing functionality of the .desktop file approach I listed above, and
would be most effective if standardized as a FreeDesktop.org standard, which I
imagine would be rejected for precisely that reason.
I don't think there any way for the system to parse the script file and guess
whether it should be opened in an interactive terminal or executed silently.
That's always going to be super fragile, and the developer of the script is in
the best position to make this kind of determination.
Moving to KIO for further discussion.
--
You are receiving this mail because:
You are watching all bug changes.
