Use Growl to monitor long-running shell commands

Search

Don't have an account yet? Sign up as a New User
Lost your password?

No new hints

No recent new links

Here are some of my (robg) other projects...

•	The Robservatory My blog - Macs, tech, etc.
•	Mac OS X Power Hound The best of Hints in print
•	Inside iWork An iWork training DVD
•	Macworld Column, features, online...

What version of OS X are you running as your main OS?

Other polls | 11,488 votes | 42 comments

Use Growl to monitor long-running shell commands | 22 comments | Create New Account

Click here to return to the 'Use Growl to monitor long-running shell commands' hint

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Use Growl to monitor long-running shell commands
Authored by: sapporo on Fri, Oct 12 2007 at 1:40AM PDT

To debug the "Some Command" problem, you could start by adding a line to preexec() that displays the command it stores in the environment:

function preexec () {
	export PREEXEC_CMD="$BASH_COMMAND"
	echo "DEBUG: PREEXEC_CMD set to '$BASH_COMMAND'"
	export PREEXEC_TIME=$(date +'%s')
}

If that looks correct, then something goes wrong in precmd().