On Fri, 2009-07-24 at 10:22 +0200, Michael Haubenwallner wrote: > 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. >
Indeed... that's what's supposed to happen. Who wants to call uprofile? Who doesn't? > > 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?" > Atm, cd just changes dir as it is supposed to. Robert alerted us to the fact that we can trigger a PRE_CMD on most shells when a CHANGEDIR occurs. > 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. > This is the question... Call uprofile manually or detect the profile automatically? Both capabilities? Mmm... > 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? > Yes and no. ~/.uselect/ contains a bin/ environment (prepended to your PATH by /etc/profile or something) a env.d/ and most probabily something else that gets executed uppon login. This does not invalidate you having a ~/.uprofile/. uprofile will configure your ~/.uselect/ and your environment variables. Your user profile will not be interpreted by python, uprofile turns profile files (from python) into bin/ and env.d/ environment on your ~/.uselect. This may seem confusing, but that's the best way I can explain. Later this weekend will send a call for ideas/call for modules to the dev list to get everyone known with the uselect environment. I'm just finishing cleaning up the code to start commiting and using git branches. > > Thank you! > I thank you! All! Have a nice weekend! > > /haubi/ > Cheers, Sérgio -- Sérgio Almeida - meph...@gmail.com mephx @ freenode
signature.asc
Description: This is a digitally signed message part