Freddie Sackur
Freddie Sackur
About the module warnings on non-canonical verbs, try this: ``` # .psd1 FunctionsToExport = @('Do-Stuff') # .psm1 # Don't dot-source the command directly $SomeModuleVariable = 42 Set-Item Function:\Global:Do-Stuff $(& {....
My team enforces long help blocks at the top - my preference is to fold those windy regions and just read the code. I would love a feature like `powershell.editor.foldHelpBlocks`.
I do still see the issue in VS Code 1.64.2 with the PS Preview extension in the PS Integrated Terminal using PSv7.2.1: ``` ### Environment PSReadLine: 2.2.0-beta5 PowerShell: 2022.2.0 OS:...
If we can get an acceptable req, I would PR it. I'd love to contribute.
I would love to PR this, but I see some development is happening off the master branch. I see that Jaykul is actively working on the build process, and I'm...
No, thank YOU. I'll pick this back up when my day job calms down a little.
I believe that the debug output ` INFO subprocess: Starting process: ["C:\\windows\\System32\\WindowsPowerShell\\v1.0\\/powershell.EXE", "-NoLogo", "-NoProfile", "-NonInteractive" # ... etc ...` can be recreated manually with: `Start-Process "C:\\windows\\System32\\WindowsPowerShell\\v1.0\\/powershell.EXE" -ArgumentList "-NoLogo", "-NoProfile", "-NonInteractive"...
I can't reproduce the issue on Windows 10 update 1607, but I can on 1803.
I would be pleased to PR the doc addition if maintainers think this should be done.
Possibly related? #1775