Re: default environment variables

[Travis Griggs]

Richard Frith-Macdonald wrote:
> On Thursday, February 27, 2003, at 10:15  pm, Travis Griggs wrote:
>
>  > What is the right way to get these set? I had added the line:
>  >
>  > . /usr/lib/GNUstep/System/Makefiles/GNUstep.sh
>  >
>  > to the end of my .bash_profile.
>
> That looks ok.
>
>  > That made it so I could compile. But it also made it os that when ever
>  > I opened a new konsole (any xterm really), I would get the series of
>  > .
>  > .
>  > make_services[2117] File NSDictionary.m: 504. In [GSMutableDictionary
>  > -initWithContentsOfFile:] Contents of file
>  > '/home/travis/GNUstep/Defaults/.GNUstepDefaults' does not contain a
>  > dictionary
>  > 2003-02-27 14:12:24.964 make_services[2117] Unable to load defaults
>  > from '/home/travis/GNUstep/Defaults/.GNUstepDefaults'
>  > 2003-02-27 14:12:25.169 make_services[2117] File NSDictionary.m: 504.
>  > In [GSMutableDictionary -initWithContentsOfFile:] Contents of file
>  > '/home/travis/GNUstep/Defaults/.GNUstepDefaults' does not contain a
>  > dictionary
>  > 2003-02-27 14:12:25.170 make_services[2117] Unable to load defaults
>  > from '/home/travis/GNUstep/Defaults/.GNUstepDefaults'
>  > 2003-02-27 14:12:25.379 make_services[2117] File NSDictionary.m: 504.
>  > In [GSMutableDictionary -initWithContentsOfFile:] Contents of file
>  > '/home/travis/GNUstep/Defaults/.GNUstepDefaults' does not contain a
>  > dictionary
>
> Either your '/home/travis/GNUstep/Defaults/.GNUstepDefaults' file is
> corrupt or there is something seriously wrong (in a way I've never
> heard of) with the software.  Your best bet would simply be to delete
> the '/home/travis/GNUstep/Defaults/.GNUstepDefaults', and if that was
> the problem things should then work ok.  However, I'd like to see a
> copy of the file in case I can figure out how it got corrupted
> (assuming this is not just a case of you having edited it manually),
> please send me (not the list) a copy before you delete it.

Thank you for the hints. I have succeeded in getting it to work. It was 
indeed corrupt but not in the normal way of "corrupt." The problem was 
that the file's permissions were -rw------- AND that its owner was root. 
chown'ing it to me made everything work fine. I don't know how it 
happened. I haven't done a lot with this stuff yet. Just apt-get to 
install the packages (which runs as root, did that cause the problem?), 
and followed a couple of tutorials. My biggest frustration with the 
installation, was that it did not even inform me that I might want to 
add that line to my .profile, thus none of the commands in the tutorials 
worked to begin with.

--
Travis Griggs
Key Technology
One Man's Pink Plane is Another Man's Blue Plane