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,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: 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