|
|
MANPATH should not be manually set
First, claiming that MANPATH shouldn't be manually set is bogus; if you don't do something like But this actually highlights another problem with the csh environment in recent Jaguar builds. Originally, Apple included in the default login scripts code to look in ~/Library/init/tcsh for extra shell initialization code. Sometime after 10.2, Apple removed this support from the default scripts; breaking me pretty thoroughly. Now you have to manually copy and rename the /usr/share/tcsh/examples to get the functionality back. Now, with Panther, Apple has apparently decided to change the default shell altogether, apparently to appease the Linux crowd. I can't wait to see what happens to fink when they do that! ---
MANPATH should not be manually set
Read the previous posts. You don't have to manually set your
MANPATH for darwinports or fink.
As for default shells, just use
So your solution
to the problem of manually set manpaths is to manually set the manpath config?
So your solution
I suppose it's really a matter of taste, but here's my take on it...
So your solution
I don't know whether it works in tcsh, but in sh/bash, the simple solution is
export MANPATH=`manpath`:/sw/share/man
chsh
Indeed. You can change your shell. All the less reason to change the default shell, forcing changes to many 3rd party apps (like fink) |
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.09 seconds |
|