PSReadLine VS PowerShell

sets up PSReadLine: command autocompletion and many other features.

Sounds like a bug, you should report it to PSReadLine. I believe PSReadLine and not PowerShell is the one that handles tab completion here, it sounds like it's caching the alias target so still thinks it is completing Get-ChildItem.

I then used PSReadLine's GitHub to understand how they made their own module, shared data with Cmdlets and everything inbetween. Which got me the rest of the day.

Highly recommend checking out the team’s sample file: https://github.com/PowerShell/PSReadLine/blob/master/PSReadLine/SamplePSReadLineProfile.ps1

I have a hotkey that converts aliases on the command line when I hit alt+% That makes it easier to paste into discord or wherever. Why % ? I'm not sure, that's what what PSReadLine used

GitHub - PowerShell/PSReadLine: A bash inspired readline implementation for PowerShell

Bit late, but it's PSReadLine

Just a bit of a heads up. The PSReadLine 2.2.0 beta 1 and beta 2 do not work with this release so either you can downgrade to PSReadLine 2.1.0 or stay on PowerShell 7.2.0 preview 5. The PSReadLine 2.2.0 beta 3 will solve the issue.

The PSReadline update-help failing is new and should probably have an issue filed on their github, assuming there isn't one already. The failure on "WindowsUpdateProvider" has been around for years, you're missing help for these cmdlets without it

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.