Vista - New Window vs Inline

I'm not quite unterstanding when Powershell decides to open a new
command window vs. a command is run inline. For example:

PS> .\python-script.py

Opens a new window.

PS> python python-script.py

Does not. Is there a way to change this behaviour?

Michael

On Jun 18, 11:17*am, Michael Elsdörfer <mich...@xxxxxx>
wrote:Michael,

In your first example, "PS> .\python-script.py", PowerShell just
executes the file based on the association with the file's extension;
it basically passes the responsibility off to python.exe, which opens
a new console window and executes the file. It is just like opening a
text file ("PS> .\file.txt") or a Word document ("PS> .
\document.doc").

In the second example, you are specifying the name of an executable
that has a command-line interface, along with a command-line
parameter. Since that application can run in the PowerShell console,
it does.

I hope this clears things up a little.

Jeff

What is in your PATHEXT environment variable? I guess, extension ".py" is
not there. Try to add and see if it helps.

--
Thanks,
Roman Kuzmin

http://code.google.com/p/farnet/
PowerShell and .NET in FAR Manager


"Michael Elsdörfer" <michael@xxxxxx> wrote in message
news:OFD4KpP0IHA.3648@xxxxxx

Roman Kuzmin schrieb:Didn't even know about PATHEXT - that does what I want. Thanks (Jeff too)!

Michael

Thats a great observation Jeff.
Because. basically the fileassociation is doing the same as
[system.diagnostic.process]::start which will always open a new process
totally seperate from your console.. But when its the plain powershell
invocation, powershell knows that its a console application and runs it
through the same console.

The same test can be done in cmd.

in CMD.exe

type CMD.EXE

you get your new childshell inside the same console window

then try

START CMD.EXE

this spawns a totally new process, and its in a new window.


Jeff wrote: