[Konsole-devel] [Bug 240758] Indicate waiting for user input

Jekyll Wu adaptee at gmail.com
Tue Sep 13 12:45:37 UTC 2011


https://bugs.kde.org/show_bug.cgi?id=240758





--- Comment #5 from Jekyll Wu <adaptee gmail com>  2011-09-13 12:45:37 ---
(In reply to comment #4)
> 

While I agree the notification for those listed examples is useful, I do not
agree with that 'Most of time'. Such long running commands are the minority,
not the majority. Most commands executed in the shell are either
interactive(vim,less,mc), or finish its work quickly(ls,cat,date) and the shell
waits for user input again almost immediately. 

So I would repeat my opinion again: waiting for user input is the most common
state. If the proposed notification for waiting for input is done, then each
time after users have executed 'ls','pwd', or 'date' and shell waits user input
again, should they be notified "the shell is waiting for input"? That would be
more boring than helpful. That notification may be designed as one-shot to
avoid such annoyance, of course.

And I think the current 'Monitor activity/silence' works well for monitoring
most long-running commands. For example, I can use 'Monitor silence' to notify
myself that wget(1) or make(1) has finished its job. Or, I can use 'Monitor
activity' to monitor some long-running calculation which does not  generate
output until it finishes.There may be some situations where 'Monitor
activity/silence' is not good enough, but I think they are the minority of the
minority.

That proposal sounds nice, but I do not think it is good/useful enough to pay
off the implementation cost and the potential side effect.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the konsole-devel mailing list