Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Use Growl to monitor long-running shell commands' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Use Growl to monitor long-running shell commands
Authored by: kyngchaos on Oct 11, '07 08:42:57PM

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.



[ Reply to This | # ]
Use Growl to monitor long-running shell commands
Authored by: sapporo on Oct 12, '07 01:40:45AM
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().

[ Reply to This | # ]