|
|
How to avoid these problems
There's a lack of defensiveness all round, here!
How to avoid these problems
Right -- I was going to point out that any decent .cshrc script which defines interactive features (aliases, etc.) needs to have an exit mechanism which bails out early for non-interactive shells. The installer application which launches a user shell is a non-interactive situation. Prior to the exit logic (where you check the prompt variable, and exit or skip if the prompt is not pre-set), the usual action would be to define the command path (set path ...). After the prompt check, you can put the terminal setting commands, command aliases, and other stuff. I thought (from years ago) that the csh (or cshrc) man page does mention this; Larry. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.08 seconds |
|