public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sérgio Almeida" <mephx.x@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-soc] Re: Progress on Universal Select Tool
Date: Thu, 23 Jul 2009 14:35:00 +0100	[thread overview]
Message-ID: <1248356100.8713.11.camel@thedude> (raw)
In-Reply-To: <8b4c83ad0907222232o6499fcbcjce1d8a063d93d5c1@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

On Thu, 2009-07-23 at 11:02 +0530, Nirbheek Chauhan wrote:
> 2009/7/23 Sérgio Almeida <mephx.x@gmail.com>:
> > A child process cannot (or shouldn't be able to) change parent's process
> > environment.
> >
> > uprofile will need to change env var's on-the-fly. For instance tag $PS1
> > with the current profile in use
> >
> 
> I don't understand what use this feature has. Won't the "current
> profile" be persistent across shells? If so, won't PS1 not be
> persistent if you change in on-the-fly? If you don't intend to keep it
> persistent, what's the use? (Actually, I don't see the use of having
> it at all)
> 
> 

Nirbheek,

You will have a persistent profile across shells and you can change it.
(This one requires sourcing). A capability of having a profile per
folder (like a folder .uselect per profiled folder)  was discussed
previously in these lists. (Actually prior to the start of SoC) I still
consider this a great feature. You changedir, you call uprofile, and
voila, new profile. You login again, default profile.

Cheers,
Sérgio
-- 
Sérgio Almeida - mephx.x@gmail.com
mephx @ freenode


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-07-23 13:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-16 14:48 [gentoo-dev] Progress on Universal Select Tool Sérgio Almeida
2009-06-17 18:32 ` [gentoo-dev] " Sérgio Almeida
2009-06-29 18:50 ` Sérgio Almeida
2009-06-29 19:02   ` [gentoo-dev] Re: [gentoo-soc] " Sebastian Pipping
2009-06-29 19:42     ` Sérgio Almeida
2009-07-13 15:36 ` [gentoo-dev] " Sérgio Almeida
2009-07-14  9:20   ` Michael Haubenwallner
2009-07-15 15:42     ` Sérgio Almeida
     [not found]     ` <1247582117.3651.3.camel@thedude>
     [not found]       ` <1247584057.14345.29.camel@sapc154.salomon.at>
2009-07-15 15:43         ` Sérgio Almeida
2009-07-16  6:22           ` Michael Haubenwallner
2009-07-22 18:41 ` Sérgio Almeida
2009-07-23  3:09   ` [gentoo-dev] Re: [gentoo-soc] " Nirbheek Chauhan
2009-07-23  4:43     ` Sérgio Almeida
2009-07-23  5:32       ` Nirbheek Chauhan
2009-07-23 13:35         ` Sérgio Almeida [this message]
2009-07-23 15:28           ` Robert Buchholz
2009-07-23 18:33             ` Sérgio Almeida
2009-07-24  8:22               ` Michael Haubenwallner
2009-07-24 15:20                 ` Sérgio Almeida
2009-07-27  8:33                   ` Michael Haubenwallner
2009-07-27 18:35                     ` Sérgio Almeida
     [not found]         ` <6f8b45100907230047k44111c77ha1b68e61b8c88bf2@mail.gmail.com>
2009-07-23 13:40           ` Sérgio Almeida
2009-07-23  6:12     ` [gentoo-dev] " Duncan
2009-08-01 18:46 ` Sérgio Almeida
2009-08-18 15:23 ` Sérgio Almeida

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1248356100.8713.11.camel@thedude \
    --to=mephx.x@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox