As a sample, the benefit of using Out-GridView is that it's available by default. While for Out-ConsoleGridView, it requires a user to install that module first. So, for the purpose of a sample, we should continue to use Out-GridView here.

However, if you can publish your handler script that uses Out-ConsoleGridView as a gist, we may be able to point to it in the comment of the F7 example.

As a sample, the benefit of using Out-GridView is that it's available by default. While for Out-ConsoleGridView, it requires a user to install that module first. So, for the purpose of a sample, we should continue to use Out-GridView here.

However, if you can publish your handler script that uses Out-ConsoleGridView as a gist, we may be able to point to it in the comment of the F7 example.

Ok, but two points that might influence you:

1. Out-GridView only works on Windows and Mac. Not Linux.
2. Out-GridView is deprecated by Microsoft.

I'm not aware that Out-GridView is to be deprecated. But you are right on the 1st point. So, if you can publish the "F7 with Out-ConsoleGridView" gist, we can consider point to it in the sample.

I forgot to mention: I've recently packaged F7History up as a PowerShell Gallery-installable module:

https://github.com/gui-cs/F7History/

With this, perhaps this PR is really about just pointing to the F7History repo as a good example?

Install F7History from the PowerShell Gallery.

Install-Module -Name "F7History"

Add a line to import F7History in your PowerShell $profile:

Import-Module -Name "F7History"

To change the key bindings, use the -ArgumentList parameter when importing the module. For example, to use F6 and Shift-F6 instead of F7 and Shift-F7:

Import-Module -Name "F7History" -ArgumentList  @{Key = "F6"; AllKey = "Shift-F6"}

The comment of the F7 sample was updated to point to the F7History module.