|
|
Use Growl to monitor long-running shell commands
Amazing work here, especially the bash code for doing this. Even with how customized I've got bash to be, zsh seems to incorporate many of the great features that don't require scripts like this to be created.
Use Growl to monitor long-running shell commands
1) Not unless you improve preexec.bash to allow this. It explicitly states:
"Note: this module requires 2 bash features which you must not otherwise be using: the "DEBUG" trap, and the "PROMPT_COMMAND" variable. preexec_install will override these and if you override one or the other this _will_ break". 2) Depending on your shell usage pattern, yes, there will be false positives (notifications you don't need or want). I thought about a white/blacklist approach, but it's too much hassle for my taste. I like to keep stuff like that simple, and I don't mind the false positives. They do distract me for a second, but I still prefer that to having to decide in advance whether or not I'll be notified. Making that decision in advance each time I execute a shell command would take me more time than looking at a superfluous notification once in a while. And while this setup works fine for me, I consider that a technique rather than a product, so go ahead and tweak it to your tastes.
Use Growl to monitor long-running shell commands
as for #1, i use a different technique which may be of use to you in this scenario. specifically, the steps below do not use PROMPT_COMMAND. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|