[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Env["PWD"], why not?
[Thread Prev] | [Thread Next]
- Subject: Re: Env["PWD"], why not?
- From: Bruce Steers <bsteers4@xxxxxxxxx>
- Date: Sat, 19 Apr 2025 11:07:23 +0100
- To: user@xxxxxxxxxxxxxxxxxxxxxx
On Fri, 18 Apr 2025 at 23:30, Benoît Minisini < benoit.minisini@xxxxxxxxxxxxxxxx> wrote: > Le 19/04/2025 à 00:22, Bruce Steers a écrit : > > Using PWD env to set working dir is cool but why not obey the global > Env[]? > > > > Ie. this works.. > > Shell "ls" With ["PWD=/usr"] Wait > > > > but this does not.. > > Env["PWD"] ="/usr" > > Shell "ls" Wait > > > > Could Shell and Exec not obey the global Env[] if it's been modified? > > then the answer to "can you set the shell working dir?" could be > > differently, "yes" :) > > > > I cannot imagine it requires much code change. (i could be wrong) > > > > Respects > > BruceS > > > > It's an hack that actually should have nothing to do with environment > variables. So there is no good reason to extend the logic of that hack. > > Regards, > > -- > Benoît Minisini. a hack? dang the other day it was an undocumented feature :( Seemed to me like a handy feature. Oh well. Thanks for the reply. I could "hack" Shell easy enough by adding "cd " & Shell(sDir) & "; " to the start of the command string but how could i hack Exec as it's only single commands? Respects BruceS
Re: Env["PWD"], why not? | gbWilly <gbWilly@xxxxxxxxxxxxxx> |
Env["PWD"], why not? | Bruce Steers <bsteers4@xxxxxxxxx> |
Re: Env["PWD"], why not? | Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx> |