|
From: Harlan S. <Har...@pf...> - 2002-10-12 01:51:35
|
The speed thing is relative. I also notice the "slowness" of modules. One issue that makes this worse for me (and probably for Andy, as he and I set this up where he is working) is that there are two ways to handle shell RC stuff: - do most things once at login time - do nothing special at login; do everything at each shell startup Over the years I have had enough trouble with the former (do it once per session, at startup) that I now reset the shell "setup" (I didn't want to say "environment") on every new shell process. The biggest problem I see with "do it once" is that "often enough" some chain of events will run a security-conscious program that scrubs the PATH or other environment things and then calls sub-processes, and if/when these sup-processes find their way back into one of my project scripts I need my expected path and other environment variables. I hope I described this clearly... If there is a better way to go I'd love to know about it. H |
