Use Growl to monitor long-running shell commands

Search

From our Sponsor...

User Functions

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

What's New:

Hints

No new hints

Comments last 2 days

Links last 2 weeks

No recent new links

What's New in the Forums?

The Editor's Corner...

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...

Hints by Topic

News from Macworld

The macosxhints Poll

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

Other polls | 11,406 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: kyngchaos on Thu, Oct 11 2007 at 8:42PM PDT

I don't think sourced shell init files need to be executable. .bash_profile isn't. I didn't make .preexec.bash executable, and it works for me.

But I do have the unhelpful "Some command" message.

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().