search

PowerShell / PowerShell-RFC

RFC (Request for Comments) documents for community feedback on design changes and improvements to PowerShell ecosystem
MIT License
430 stars 123 forks source link

PS Community Call for November 19, 2020 #266

Closed joeyaiello closed 3 years ago

joeyaiello commented 3 years ago

Please add topics and questions for the November 19, 2020 Community Call here.

Agenda:

kvprasoon commented 3 years ago

Update about Working groups ? I see WG-* labels out there.

iSazonov commented 3 years ago

I would like to say a big thank to @xtqqczze for his great job modernizing PowerShell codebase (style, formatting, forcing analyzer rules).

ThomasNieto commented 3 years ago
rkeithhill commented 3 years ago

Any plans to get overall better native exe support into 7.2 or is that an 8.0 thing?

ili101 commented 3 years ago

Will there be a day when we will be able to copy paste random code from the internet like dig @8.8.8.8 github.com to PowerShell and it will just work? Is this in the scope of https://github.com/PowerShell/PowerShell/issues/1995? If it is will it be merged in some point? as I understated it's a braking change but it will be a beneficial as it will make PowerShell compatible with all the other terminals like cmd and bash.

EDIT: @rkeithhill you beat me to it by a few seconds (:

ThomasNieto commented 3 years ago

Specifically about question marks as valid characters in variable names. Last community call the PS team indicated that they would be looking back into the issue. @mklement0 request is to reopen the issue as analysis of the PowerShell corpus found that virtually no one uses question marks in variable names.

mklement0 commented 3 years ago

@ili101:

Is this in the scope of PowerShell/PowerShell#1995?

No, PowerShell/PowerShell#1995 is about fixing the broken argument-passing to external programs when you use PowerShell's syntax.

By contrast, PowerShell/PowerShell#13068 is what you're referring to: the ability to call a command that uses another shell's syntax without modification.

As seductive as that is, I think it is a dead end that will create more problems than it will solve, similar to the problematic --%.

Hence my suggestion to not fight PowerShell's syntax and instead provide an ins (Invoke-NativeShell) cmdlet that takes the command as a string: ins 'dig @8.8.8.8 github.com'

See https://github.com/PowerShell/PowerShell/issues/13068#issuecomment-660263405, https://github.com/PowerShell/PowerShell/issues/13068#issuecomment-661984949, and https://github.com/PowerShell/PowerShell/issues/13068#issuecomment-671572939