PowerShell-Docs VS PowerShell

--% is a half-baked solution and has various inherent issues. It should not be relied upon if alternative solutions exist.

They seem to have an internal system that is triggered by commits on the main branch on those repositories that contain docs. For example, if you look at https://github.com/MicrosoftDocs/PowerShell-Docs, and click on the commit checks for the latest main commit (green checkmark next to the commit), there is one check "OpenPublishing.Build" that leads to the report of where the files were uploaded: https://opbuilduserstoragepublic.blob.core.windows.net/report/2022%5C5%5C5%5C6ff7e8c3-dfc6-3ebd-da5a-d5e2ff43de8f%5CPullRequest%5C202205052157488348-8793%5Cworkflow_report.html?sv=2021-04-10&se=2022-06-05T21%3A59%3A48Z&sr=b&sp=r&sig=VsulIs3Vw8QappOaWIin6%2FqLJN5M99%2FATZiOWFF3k0U%3D

This might be useful: https://github.com/MicrosoftDocs/PowerShell-Docs/issues/5665

Then I found this. But there is no doc in here related to my issue.

Yes on the main page -- Click on the Green Code Button, then click Download Zip. It will work better if you have a copy of the GitHub desktop client, but its not technically necessary.

Sorry to break it to you, but Preheat is not an approved Powershell verb :(

This issue explains the reason. Get-Service was using DCOM, which has been removed.

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901

PowerShell is available on macOS and Linux as well (source on Github: https://github.com/PowerShell/PowerShell). It may not be as well-integrated with things like system services management, but the language still works well. You can still use all the command line tools you're used to on Linux, of course.

nushell does look interesting, though the lack of a .deb repository does put it pretty low on my to-do list.

Issue #7940 discusses potential improvements to array slicing.

Note: This can be problematic as it prevents upstream commands from running their end {} block. See here. The new clean {} block introduced in PowerShell v7.3 does not suffer from this issue.

Can you give an example of something that PS can do that is built-in for text processing, instead of a proprietary symbolic query language?

[1] https://github.com/PowerShell/PowerShell

https://github.com/PowerShell/PowerShell/blob/master/LICENSE... is the MIT license. (Microsoft supplies debs directly which may reduce the motivation for Debian to do so.)

Oh, heh, also https://github.com/PowerShell/PowerShell/blob/master/docs/bu... the build script is written in PowerShell, so there's a bootstrapping problem :-) (Debian has solved those before of course, but with community sentiment like the above maybe noone is motivated to bother.)

According to https://github.com/PowerShell/PowerShell/issues/19628, the default behaviour is invoked whenever the completion script returns no output. To attempt to do so, I tried exiting the script via returning an empty string, or using the return keyword to exit the script completely, unfortunately with no avail. Is there a technique to achieve what I want, and is there any documentation about it other than the official one? Thank you in advance.