Re: powershell compatible SPP
[email protected] (Chris Marshall) Sat, 1 Jul 2017 11:32:26 -0400
| Newsgroups | perl.win32.vanilla |
|---|---|
| Message-ID | <[email protected]> |
On 6/30/2017 23:54, [email protected] wrote: > -----Original Message----- From: Chris Marshall > Sent: Saturday, July 01, 2017 5:16 AM > To: [email protected] > Subject: powershell compatible SPP > > Hi Chris, > >> Following a conversation with Chas Owens at YAPC::NA 2017 in >> Alexandria, we're working on an implemention of SPP using Windows >> PowerShell rather than command.com and .bat files. > > On a Windows 10 laptop, I opened a powershell (for the first time in > my life) and added the location of SPP's gcc and perl bin folders to > the path: > > PS C:\p> > $Env:Path="$Env:Path;C:\_64\strawberry5.24.0-ld\c\bin;C:\_64\strawberry5.24.0-ld\perl\bin" > > (I'm not proposing that as the solution - I would think you'd want to > provide an alternative to portableshell.bat that does that for the user.) Yes, something like portableshell.ps1 > But does that provide the functionality that's required ? ... or are > there some issues regarding the functionality thus obtained ? The main one is without command.com, all the .bat files for running perl scripts as programs (think pdl2 or perldl) won't run. I was thinking to replace the batch files with PowerShell functions (or cmdlets as they call them). > It seemed fine to me - whereas running SPP's portableshell.bat from > inside an already existing powershell seemed to bugger up the shell's > behavioural characteristics. > Can't run .bat files wihout a command.com. I'm hoping for a next generation portable shell dot bat. Cheers, Chris