[sage-devel] Re: sage -sh changes

2009-10-27 Thread William Stein
On Tue, Oct 27, 2009 at 9:06 AM, ghtdak wrote: > > Someday I guess I'll go and see what I might be doing different than > whats expected or normal...  Shell programming and management is a > magical world that I don't claim to have conquered and very simple > changes to the .*rc files can have ma

[sage-devel] Re: sage -sh changes

2009-10-27 Thread ghtdak
Someday I guess I'll go and see what I might be doing different than whats expected or normal... Shell programming and management is a magical world that I don't claim to have conquered and very simple changes to the .*rc files can have massive unintended consequences. In my case, when I get the

[sage-devel] Re: sage -sh changes

2009-10-26 Thread Jaap Spies
William Stein wrote: > 2009/10/26 Glenn Tarbox, PhD : >> Beginning with Release 4.1.2, "sage -sh" was adjusted and now completely >> strips the users environment as set in the various .*rc files. >> > > After I read this, I expected the following would happen: > > d-69-91-158-18:~ wstein$ expor

[sage-devel] Re: sage -sh changes

2009-10-26 Thread William Stein
2009/10/26 Glenn Tarbox, PhD : > Beginning with Release 4.1.2, "sage -sh" was adjusted and now completely > strips the users environment as set in the various .*rc files. > After I read this, I expected the following would happen: d-69-91-158-18:~ wstein$ export FOO="bar" d-69-91-158-18:~ wstei