Repository navigation
[FR] Allow Output from External Program to Be Captured and Displayed #963
Replies: 4 comments
|
That sounds like a great idea, definitely a lot of use-cases. Even better if the popup supported |
|
Would love to see an option to interact with a running external program if it is a terminal app. I kinda hoped that when reading about this feature it would just pop up a little terminal window in the browser with stdin and stdout that persisted until the external program exited. Would be nice for people who run post-processing scripts on saved downloads to monitor or give input when necessary. |
|
This appears to be related to:
Both requests involve capturing and displaying output from external programs. |
Agent BriefCategory: enhancement Current behavior: Desired behavior:
Key interfaces:
Acceptance criteria:
Out of scope:
Why a human: Feature scope is a maintainer call. Also decide whether the output is only shown in a dialog or also saved in the activity log, which #1047 asks for. |
Uh oh!
There was an error while loading. Please reload this page.
Saving and displaying the output from a non-interactive external program has lots of possibilities for use cases. For me I'd like the ability to run mediainfo against a file quickly from the qui interface and get the output in a little popup window.
In my mind whether output is captured or not should be an option on the external program and the popup should have an easy way of copying the result. But of course feel free to implement however you think is best :P
P.S. if you'd rather I just make a feature request for a mediainfo integration I understand. I'm just assuming you'd rather have a more general solution.
All reactions