Keith Hill

Early on the extension didn't have a custom host and debug input/output happened via the Debug Console. I think we suppressed profiles back then. The addition of the "temporary console"...

You can search backwards with Ctrl+r. If you go too far, use Ctrl+s to move forward through the matching history list.

Possibly but the point, I think, is that PSReadline (inspired by GNU Readline), was created to provide such features. `Get-History` is legacy command that is still useful IMO as more...

@gwojan Thanks for confirming the issue.

@daxian-dbw AFAICT nothing is saved in the history file if you use `SaveAtExit`. 🤷‍♂️

The extra number in parens is the process id of the PowerShell process. Useful if you need to attach a debugger to (or kill) the process.

The Engine WG reviewed this issue and agrees with @Luiz-Monad. The message can easily be updated to display the int `ExitCode` in both decimal and hexadecimal.

The Engine WG reviewed this issue today and agree that it is a bug that needs to be investigated for a potential fix.

We've also seen people have issues with this in VSCode with the PowerShell extension. This crops up when you select script that refers to $PSScriptRoot and press F8 to run...

Perhaps a more PowerShelly way to implement this would be to add a parameter like `-Parameters` e.g: ```powershell set-alias gc git -parameters commit, "--a" # OR maybe -Parameters allows a...