PowerShell alongside cmd.exe as your command line options?

[Ron_Green]

From our last Townhall, a request was made for us to change our Fortran Windows compiler  Command Windows with PowerShell.

Obviously we cannot simply swap out cmd.exe with PowerShell.  It would break too many people in our community.  

The setvars.bat for cmd.exe does not work with PowerShell.  So we'd need a new setvars-ps.bat or some new script file to set environment. 

And we'd have to get all the other oneAPI components to agree to a new oneAPI level setvars that is for PowerShell.

But at a high level - should we pursue having both the old cmd.exe capabilities you have today BUT provide an option for using PowerShell instead?  Keep cmd.exe as default so we don't break anyone, but provide a Start menu item under oneAPI for a PowerShell window instead of a cmd.exe window?

I wonder if PowerShell is the command line env of choice.  Or would power users simply use WSL linux window?  

Your feedback would be welcomed.  What would you want to see for command line windows?

[mecej4]

On Windows, I use CMD most often, Bash+Cygwin sometimes, and Powershell almost never.

Please do not remove CMD support unless the majority of IFort users indicate that they do not use CMD anymore.

[Ron_Green]

We'll keep cmd support.  PowerShell would be 'in addition' and optional.

[Arjen_Markus]

The same holds for me. I have never found much reason to learn PowerShell - the various Unix-style shells and Windows' cmd work for me. So, please do not remove cmd support.

[mKlapwijk]

Personally I would like this a lot. I can never get used to cmd prompt, and use PowerShell whenever I have to work on Windows (mostly since it is more similar to a Linux shell, and several aliases are similar).

My current working method is having a Powershell function which calls cmd to run the setvars.bat, and then return:

function cmdSetIntelVarsReturnPS {
     cmd.exe "/K" '"C:\Program Files (x86)\Intel\oneAPI\setvars.bat" && pwsh' }

but having this out of the box would be more convenient.

I agree that removing cmd support is not the way to go, but having a Powershell equivalent  of the setvars script would be very useful.

[Steve_Lionel]

Microsoft has made it clear that they consider PowerShell to be the future. I do think Intel should be proactive and provide scripts and shortcuts that work in PS, and not wait until their hand is forced. I do NOT think power users would prefer WSL - I think the usage of WSL is quite low among the user base. Windows users would typically be offended if it was suggested they use WSL instead.