https://bugs.kde.org/show_bug.cgi?id=459843
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |n...@kde.org
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #7 from Nate Graham <n...@kde.org> ---
To me it definitely makes sense to send a notification with command output for
commands that write to STDOUT and then exit. Once the process exits, we can
gather up the output and stick it right in a notification.
If the command keeps running, I think it could still make sense if we have the
ability to keep the notification with command output visible on screen and
update its text in real time as the process writes more text. If we don't have
the technical ability to do that, or it's not feasible, IMO it's sane enough to
preserve the status quo and let the process just keep running silently, as this
is a very niche use case and I think it's safe to assume that a user who does
this knows what they're doing!
--
You are receiving this mail because:
You are watching all bug changes.
