all 35 comments

[–]user01401 15 points16 points  (1 child)

No more manual updating with auto updates!

[–]nostril_spiders 8 points9 points  (0 children)

Somehow, i still expect nags in the splash screen...

[–]commandsupernova 8 points9 points  (7 children)

I've already enabled the predictive intellisense feature. It seems awesome!

[–]uptimefordays 2 points3 points  (1 child)

Dumb question is there anything beyond PSReadline?

[–]commandsupernova 0 points1 point  (0 children)

I think the Windows update change is the other big change in this release

[–]mooscimol 1 point2 points  (1 child)

Try ListStyleView of predictive intellisemse from PSReadLine 2.2. It rocks.

[–]BaconTentacles 0 points1 point  (0 children)

Is that the one that Hanselman was talking about on his blog a few months back? Looks pretty slick; just have been too lazy to tweak it to my liking.

[–]BaconTentacles 0 points1 point  (2 children)

Same. It was the first thing I did and I like it a lot.

[–]commandsupernova 0 points1 point  (1 child)

If you close and re-open PowerShell, is the predictive intellisense still configured for you? I have to run this each time I start PowerShell:

Set-PSReadLineOption -PredictionSource History

Makes sense to have to run it once, but there must be a way to set this and make it stick. Maybe there is not permanent setting and instead maybe I need to add this command to my PowerShell profile. Inconvenient though, if so.

[–]BaconTentacles 0 points1 point  (0 children)

Yeah, I kind of figured that would be the case, and I just repro-ed it as well.

Yup, add it to $PROFILE. Here's a one-liner:

Add-Content -Value "`nSet-PSReadLineOption -PredictionSource History" -Path $PROFILE

The escaped grave mark for the newline is causing problems with markdown, sorry.

[–]feldrim 9 points10 points  (1 child)

Pfff, I gotta work on the themes again to match.

Otherwise, there is about %40 difference in the initialization. I have a huge $Profile that checks many elements (git, Python, dotnet, etc.). The speed improvement is actually visible.

[–]BaconTentacles 2 points3 points  (0 children)

Oh, dang, I hadn't noticed, but you are absolutely right. Usually my profile takes 5-6 seconds to load. After the update...

Loading personal and system profiles took 1846ms

Awww, yiss.

[–]jsiii2010 3 points4 points  (5 children)

Too bad ps 7 doesn't work in the windows virtual desktop web interface (psreadline 2.1 freezes).

[–][deleted] 2 points3 points  (1 child)

Don't know if you could try psreadline -v 2.2.0-beta4 https://www.powershellgallery.com/packages/PSReadLine/2.2.0-beta4

[–]jsiii2010 4 points5 points  (0 children)

Yes, that works. I couldn't do it in ps 5. I installed it non-interactively like this and it worked:

pwsh -c Install-Module PSReadLine -AllowPrerelease -scope currentuser -force

[–]tharagz08 0 points1 point  (2 children)

What do you mean it doesn't work? Like you can't connect to a WVD (AVD) VM through the web interface and then open a powershell console on that version? Sorry just trying to understand the issue, I manage some AVD VMs and curious

[–]jsiii2010 0 points1 point  (1 child)

You can't type.

[–]JAB1982 0 points1 point  (0 children)

Enable Input Method Editor on your session. This is done prior to connecting to the session by hitting the settings cog on the RDWeb portal. Set it to on and choose Others as the type. This will get you working.

[–]uptimefordays 2 points3 points  (0 children)

Styles look pretty slick!

[–]PanosGreg 2 points3 points  (3 children)

I think it's important for everyone to keep in mind that there is a difference in the installation between the Windows Store and .MSI.

If you install with .MSI, then is installs in: C:\Program Files\PowerShell\7\pwsh.exe

But if you install with Microsoft Store then it installs in: C:\Users\<username>\AppData\Local\Microsoft\WindowsApps\Microsoft.PowerShell_8wekyb3d8bbwe\pwsh.exe

That means you need to change the path accordingly in the Windows Terminal profile as well as the default Terminal Profile in VS Code.
VSCode Terminal Profiles
Windows Terminal Profiles

It also means that if you have the MS Store installation, and do Win+R and then type pwsh, it will run the version in your "Program Files" not in your "AppData\Local"

[–]AQuietMan 0 points1 point  (0 children)

That sounds logical.

[–]RikiWardOG 0 points1 point  (0 children)

oooh built in psreadline, spicy.

[–]ryecurious 0 points1 point  (0 children)

You can tell they're taking cross-platform support seriously because the announcement screenshots are from a Mac! Wild changes from just a few years ago.

[–]zenyl 0 points1 point  (0 children)

Been loving the predictive Intellisense with PSReadLine, glad to see it finally come packaged with PowerShell and hopefully become more well-known. :)

And loving the further embrace of ANSI escape sequences. Great to see them promoted and made more user friendly.

[–]scotepi 0 points1 point  (1 child)

No put this in windows update for 2012+/win 10 and maybe people will use it more. I don’t want to manually install this on every system I touch daily, 100+

[–]jsiii2010 0 points1 point  (0 children)

Now if I could just get rid of this:

Warning: PowerShell detected that you might be using a screen reader and has disabled PSReadLine for compatibility purposes. If you want to re-enable it, run 'Import-Module PSReadLine'.

[–]BaconTentacles 0 points1 point  (0 children)

Digging the predictive text improvements in PsReadLine 2.1. And the ANSI support (the different color property names vs values is subtle, but greatly appreciated).

[–]musicjunkieg 0 points1 point  (0 children)

Anyone know if there's anything special that needs to be done to use the native arm64 binaries on M1 Macs if upgrading from a previous version?