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