Summary: | scan terminal content to activate audible or visual alarm | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | tklopp <tklopp> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
tklopp
2007-10-10 09:53:01 UTC
Most of what you say can be accomplished with grep and Konsole detecting silence / activity. Thats not true for me. The external process has been started and while waiting for the result I realize it may take long: I cannot stop the process and must wait until end. It is not possible to stop it and pipe the output through grep -- I need the output to see wether there are errors. And there are processes I cannot stop like builind an index in a big mysql database. I don't want to watch the terminal all the time -- I want to switch to another screen and do other things until a signal tells me "Hey, the process you started an hour ago is now complete!". 1. ctrl-z 2. fg ; echo $? ; printf '\a' ...will produce a bell (which makes a certain amount of "noise") after the current command completes. You can substitute the printf for anything you like. (Hmm, although if it is remote, probably not much more than the \a is useful unless you can ssh passwordless back into your machine to do stuff.) |