Michael, > Seems you didn't really understand my problem yet - another try: > The *one* and *same* user does need different settings at the *same* > time depending on the project he's currently working on in different > shells. The actual setting needs to be set up by the project's > environment script (when the users enters the project), not the user's > profile script (when the user logs in). >
Ok, now I fully understand you and I agree. A new feature? Mmm... This can be managed by profile creation and switching. Imagine, user can create a profile with it's current uselect settings, select a default profile, select the active profile on-the-fly, and on and on... Works, but not automatic... Maybe we can optimize this by having a similar behavior of .svn folders on svn settings. How about having the profile switch automatic whenever you call "uselect something" getting the current profile settings from current dir's .uselect folder? I am starting the plans on profile managing today. This now gets interesting. Thanks! Cheers, Sérgio -- Sérgio Almeida <meph...@gmail.com> mephx @ freenode
