https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #8 from Michael D ---
Sounds like a great idea, and think it would make for a very nice new feature
for the command plugin that many would find useful and welcome.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459843
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #6 from Michael D ---
Set the character limit to be roughly the limit of the notification osd. Also,
show the notification only once, e.g. after the first line of output. Seems
reasonable, but I see there are choices to be made.
--
You
https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #5 from Alexander Lohnau ---
>I think this would be fine even for long-running processes as it would just
>output the first n characters of output as a notification.
Though where would you draw the line on when to output the notification?
https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #4 from Michael D ---
Sorry for the delay. I think a notification would work better in certain
situations where you don't need a terminal window spawning, just a transient
notification giving the output. I think this would be fine even for
https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #3 from Alexander Lohnau ---
@MichaelD Does the "Run in Terminal Window" solution that Natalie mentioned
work for you?
TBH, I think implementing it as a notification would not work well. Especially
if you think of long-running processes.
https://bugs.kde.org/show_bug.cgi?id=459843
--- Comment #2 from Natalie Clarius ---
This will not trigger a notification but open a terminal window.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=459843
Natalie Clarius changed:
What|Removed |Added
CC||natalie_clar...@yahoo.de
--- Comment #1 from
