How to prevent command/script from changing global environment

Posted by guillermooo on Stack Overflow See other posts from Stack Overflow or by guillermooo
Published on 2010-05-30T22:24:11Z Indexed on 2010/05/30 22:32 UTC
Read the original article Hit count: 182

Filed under:

powershell

|

subshell

I need to run scriptblocks/scripts from the current top-level shell and I want them to leave the global environment unmodified.

So far, I've only been able to think of the following possibilities:

 powershell -file <script>
 powershell -noprofile -command <scriptblock>

The problem is, that they are very slow.

For instance, I would like to be able to do:

mkdir newdir
cd newdir
$env:NEW_VAR = 100
ni -item f 'newfile.txt'

...so that my shell's working dir wouldn't change and $env:NEW_VAR wouldn't be set in the global environment.

Are there any more alternatives to accomplish this?

© Stack Overflow or respective owner

Related posts about powershell

In Powershell on Windows7, how do I automatically set aliases (or run scripts) when powershell loads

as seen on Super User - Search for 'Super User'
I have created a powershell cmdlet and assigned it to an Alias. How do I do this automatically every time powershell launches? (i.e. so I don't have to re-assign the alias every time) >>> More
How to Load commands into your powershell profile to run on starting powershell

as seen on Server Fault - Search for 'Server Fault'
Hi, I have found a way to load exchange 2010 powershell into powershell running on a windows xp workstation, however there are a few commands that need to run. I was wondering how I could load them into a profile somehow. These are the commands that I need to run before I can do any of the exchange… >>> More
C#, Powershell - Microsoft.Exchange.Management.PowerShell.Admin

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm having troubles using the Microsoft.Exchange.Management.PowerShell.Admin on a server. The server is not the one running Exchange 2007, it's a remote server (in the same zone). I can't figure out how to add the Snapin for Powershell - Microsoft.Exchange.Management.PowerShell.Admin. Is it possible… >>> More
PowerShell Script to Create PowerShell Profile

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Utilizing a PowerShell profile can help any PowerShell user save time getting up and running with their work. For those unfamiliar a PowerShell profile is a file you can store any PowerShell commands that you want to run when you fire up a PowerShell console (or ISE.) In my typical profiles (example… >>> More
Download Free PowerShell Quick Reference Guides from Microsoft

as seen on How to geek - Search for 'How to geek'
Are you just getting started with learning PowerShell or tired of looking up less frequently used commands? Then this terrific set of PowerShell quick reference guides from Microsoft is just what you need! The first guide focuses on commonly-used Windows PowerShell commands and is available in a single… >>> More

Related posts about subshell

How to pass bash script arguments to a subshell

as seen on Super User - Search for 'Super User'
I have a wrapper script that does some work and then passes the original parameters on to another tool: #!/bin/bash # ... other_tool -a -b "$@" This works fine, unless the "other tool" is run in a subshell: #!/bin/bash # ... bash -c "other_tool -a -b $@" If I call my wrapper script like this: wrapper… >>> More
Why does subshell not inherit exported variable (PS1)?

as seen on Super User - Search for 'Super User'
After some debugging I finally narrowed down the problem as to why my X session xterm prompt does not appear according to my PS1 setting. If I run sh -c env, it doesn't even show PS1 in the list. Why? export PS1='test' sh -c env # No PS1 in the list, default prompt appearance (shell name + version) Substituting… >>> More
How to Detect that Current (Bash) Shell is a (Vi/Vim) Subshell?

as seen on Super User - Search for 'Super User'
From inside Vi/Vim, I can type: :shell to drop into a shell. Is there any way to detect that I am in a Vi-spawned subshell? The environmental variable SHLVL is 2, but that does not tell me explicitly that I am in a Vi/Vim-spawned subshell. On OS X, the following variables are also set: MYVIMRC… >>> More
bash/ksh/scripting eval subshell quotes

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi tehere, I'm using ksh and have some little troubles, could you help me? why does not this code run? [root]$ CMD="ls -ltr" [root]$ eval "W=$( $CMD )" [root]$ ksh: ls -ltr: not found. [root]$ echo $W and this works fine: [root]$ CMD="ls -ltr" [root]$ eval 'W=$('$CMD')' [root]$ echo $W Thanks… >>> More
shell scripting: nested subshell ++

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi guys, more than a problem, this is a request for "another way to do this" actually, if a want to use the result from a previous command I into another one, I use: R1=$("cat somefile | awk '{ print $1 }'" ) myScript -c $R1 -h123 then, a "better way"is: myScript -c $("cat somefile | awk '{… >>> More