From: "Sérgio Almeida" <mephx.x@gmail.com>
To: Robert Buchholz <rbu@gentoo.org>
Cc: gentoo-soc@lists.gentoo.org, Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Re: [gentoo-soc] Re: Progress on Universal Select Tool
Date: Thu, 23 Jul 2009 19:33:58 +0100 [thread overview]
Message-ID: <1248374038.8713.96.camel@thedude> (raw)
In-Reply-To: <200907231728.23329.rbu@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1667 bytes --]
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.
>
> Most shells have the ability to execute a command when a new prompt is
> generated. Users do not need to call uprofile themselves, they could
> set up their ~/.*shrc to do this.
>
> For zsh (and tcsh), you can define a function:
> chpwd Executed whenever the current working directory is
> changed.
> precmd Executed before each prompt. Note that precommand
> functions are not re-executed simply because the
> command line is redrawn, as happens, for example, when
> a notification about an exiting job is displayed.
>
> For bash, you can set a variable:
> PROMPT_COMMAND If set, the value is executed as a
> command prior to issuing each primary prompt.
>
>
> You could utilize this to call uprofile, have it output environment
> variables and set them in the shell environment. A portable (bug ugly,
> code wise) way would be to do this as part of the PS1 variable.
>
This seems interesting... The problem would be to get a unified way of
doing this with each and every shell. Can still be done but it's ugly.
I'm shure we wouldn't want it to run on every PROMPT but surely on every
chdir. We can wrap this into a PROMTP precmd...
if cmd = 'chdir':
uprofile
This gets me into coding...
What do you guys think?
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 --]
next prev parent reply other threads:[~2009-07-23 18:34 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
2009-07-23 15:28 ` Robert Buchholz
2009-07-23 18:33 ` Sérgio Almeida [this message]
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=1248374038.8713.96.camel@thedude \
--to=mephx.x@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-soc@lists.gentoo.org \
--cc=rbu@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