1 |
On Thu, 2009-07-23 at 11:02 +0530, Nirbheek Chauhan wrote: |
2 |
> 2009/7/23 Sérgio Almeida <mephx.x@×××××.com>: |
3 |
> > A child process cannot (or shouldn't be able to) change parent's process |
4 |
> > environment. |
5 |
> > |
6 |
> > uprofile will need to change env var's on-the-fly. For instance tag $PS1 |
7 |
> > with the current profile in use |
8 |
> > |
9 |
> |
10 |
> I don't understand what use this feature has. Won't the "current |
11 |
> profile" be persistent across shells? If so, won't PS1 not be |
12 |
> persistent if you change in on-the-fly? If you don't intend to keep it |
13 |
> persistent, what's the use? (Actually, I don't see the use of having |
14 |
> it at all) |
15 |
> |
16 |
> |
17 |
|
18 |
Nirbheek, |
19 |
|
20 |
You will have a persistent profile across shells and you can change it. |
21 |
(This one requires sourcing). A capability of having a profile per |
22 |
folder (like a folder .uselect per profiled folder) was discussed |
23 |
previously in these lists. (Actually prior to the start of SoC) I still |
24 |
consider this a great feature. You changedir, you call uprofile, and |
25 |
voila, new profile. You login again, default profile. |
26 |
|
27 |
Cheers, |
28 |
Sérgio |
29 |
-- |
30 |
Sérgio Almeida - mephx.x@×××××.com |
31 |
mephx @ freenode |