Vista - File association bug?

Hello,

After doing the following:

get-childitem -path envathext # for copy-paste in next command

set-item -path envathext -value
".pl;.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.PSC1"
Perl scripts such as execute: c:\no\space\path.pl
However, scripts with spaces in their path still need the prefix "perl"
need to add perl: perl "c:\path with\space.pl"
(No such problem in cmd.exe.)

--Suresh

"Suresh Govindachar" <sgovindachar@xxxxxx> wrote in message
news:%23jLKNhs$HHA.4200@xxxxxx
It's because what follows the space(s) are regarded as arguments to the
script / program, unless you use the quotes.


Some other alternatives

Invoke-Item "c:\path with\space.pl"
OR
& "c:\path with\space.pl"

Takes a bit of getting used to, though, I agree.


--
Jon

Perhaps I was not clear:
Both cmd.exe and PS require quotes around filenames with spaces.
However,
In cmd.exe, one only needs the quotes;
in cmd.exe, one need _not_ add anything to the "file name".
in cmd.exe, just typing the "file name" causes it to be executed.
But in PS one must _prepend_ the "file name" with perl or & to execute
it.

"Suresh Govindachar" <sgovindachar@xxxxxx> wrote in message
news:%23pKJZbv$HHA.1208@xxxxxx
PowerShell works slightly differently.

If you type a set of characters in quotes then it's regarded as a string,
which is why you can type things like

$apples = 3
"There are $apples apples on the shelf"

OR

$a = "apple"; "apple".ToUpper()


etc

and those statements make sense. There are a lot of advantages to this in
other areas.

But returning to the point, when you type "c:\path with\space.pl" on its
own, it's regarded as a string.


--
Jon