Pick of the Week - Nov 10 [Show all picks]
Path Finder 5 - A feature-laden Finder replacement
Submit Hint Search The Forums LinksStatsPollsFAQHeadlinesRSS
12,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 whomever posted them. This site is not responsible for what they say.
Use Growl to monitor long-running shell commands
Authored by: ScottTFrazer on Thu, Oct 11 2007 at 2:19PM PDT
This hint didn't work for me as suggested. When I created the ~/.bashrc and ~/.preexec_bash files, then restarted terminal, nothing happened. I verified that growlnotify was working, but I couldn't get anything to output.

I moved the .bashrc commands to /etc/bashrc and moved the preexec_bash portion to /etc/ as well (updating the reference in bashrc to point at the right place)

It works now, but doesn't grab the command name, reporting instead that "Some Command" took X seconds to finish. I tested with "sleep 20"


[ Reply to This | # ]
Use Growl to monitor long-running shell commands
Authored by: Red Phoenix on Thu, Oct 11 2007 at 8:02PM PDT

I ended up putting the part it said to put in ~/.bashrc in to ~/.profile. If the .profile file exists, it ignores anything in .bashrc. I do have the same problem of it saying "Some Command" still.

--
Red Phoenix
Talamathi


[ Reply to This | # ]