Sérgio Almeida wrote: > On Thu, 2009-07-23 at 17:28 +0200, Robert Buchholz wrote: >> On Thursday 23 July 2009, Sérgio Almeida wrote: >>> You changedir, you call uprofile, and >>> voila, new profile. You login again, default profile.
..., change back to your home dir, call uprofile, and you have your default (=login) environment. > if cmd = 'chdir': > uprofile > What do you guys think? While the per-directory profile sounds interesting and useful (a really good idea!), as it might solve the requirement for per-project environment here, the automatism for the 'cd' command feels like more confusing than useful: "WTF does 'cd' more than change directory?" Instead, provide a command to update the environment for the current directory, which does search for an .uprofile/ in all the parent directories when there is no local one. Additionally, (let the user) define a *new* command that does both changing directory and updating the environment. Another point: the per-directory profile solution feels like there is no need to distinguish between user- and directory-profile any more - as the user-profile would not be anything different than ~/.uprofile/, no? Thank you! /haubi/
