Cronologia persistente di Windows PowerShell

Question

Quindi ho trovato questo eccellente metodo di persisting history in Windows PowerShell.

# Persistent History 
# Save last 200 history items on exit 
$MaximumHistoryCount = 200  
$historyPath = Join-Path (split-path $profile) history.clixml 

# Hook powershell's exiting event & hide the registration with -supportevent (from nivot.org) 
Register-EngineEvent -SourceIdentifier powershell.exiting -SupportEvent -Action { 
    Get-History -Count $MaximumHistoryCount | Export-Clixml (Join-Path (split-path $profile) history.clixml) 
} 

# Load previous history, if it exists 
if ((Test-Path $historyPath)) { 
    Import-Clixml $historyPath | ? {$count++;$true} | Add-History 
    Write-Host -Fore Green "`nLoaded $count history item(s).`n" 
} 

# Aliases and functions to make it useful 
New-Alias -Name i -Value Invoke-History -Description "Invoke history alias" 
Rename-Item Alias:\h original_h -Force 
function h { Get-History -c $MaximumHistoryCount } 
function hg($arg) { Get-History -c $MaximumHistoryCount | out-string -stream | select-string $arg } 

Tuttavia quando ho incolla questo nel mio $ profilo e ricomincio PowerShell ho la seguente errore

 
Register-EngineEvent : Missing an argument for parameter 'Action'. Specify a parameter of type 
'System.Management.Automation.ScriptBlock' and try again. 
At D:\path\to\WindowsPowerShell\Microsoft.PowerShell_profile.ps1:20 char:73 
+ Register-EngineEvent -SourceIdentifier powershell.exiting -SupportEvent -Action 
+                   ~~~~~~~ 
    + CategoryInfo   : InvalidArgument: (:) [Register-EngineEvent], ParameterBindingException 
    + FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.RegisterEngineEventCommand 

Answer 1

Questo è il codice che uso da utilizzare quando ho perseverato la mia storia

$historyPath = Join-Path (split-path $profile) "history-$(Get-Date -f o).clixml" 
Register-EngineEvent -SourceIdentifier powershell.exiting -SupportEvent -Action { 
    Get-History | Export-Clixml $historyPath 
}.GetNewClosure() 

Il GetNewClosure() viene utilizzato per acquisire la variabile IIRC $historyPath.

Answer 2

Molto correlato a questa domanda è "Come posso accedere alla cronologia utilizzando le frecce su/giù?" Il modulo PSReadLine risolve questo:

Install-Package PSReadLine 

Quindi aggiungere:

Import-Module PSReadLine 

Per vostra $profile.

Answer 3

Beh, come una combinazione di codice del topicstarter e una risposta leggermente modificato da Steven Penny, questo è il pezzo pieno di codice che sta lavorando per me

################# Persistent History ############ 
# Save last 200 history items on exit 
$MaximumHistoryCount = 200  
$historyPath = Join-Path (split-path $profile) history.clixml 

# Hook powershell's exiting event & hide the registration with -supportevent (from nivot.org) 
Register-EngineEvent -SourceIdentifier powershell.exiting -SupportEvent -Action { 
     Get-History | Export-Clixml $historyPath 
}.GetNewClosure() 

# Load previous history, if it exists 
if ((Test-Path $historyPath)) { 
    Import-Clixml $historyPath | ? {$count++;$true} | Add-History 
    Write-Host -Fore Green "`nLoaded $count history item(s).`n" 
} 

# Aliases and functions to make it useful 
New-Alias -Name i -Value Invoke-History -Description "Invoke history alias" 
Rename-Item Alias:\h original_h -Force 
function h { Get-History -c $MaximumHistoryCount } 
function hg($arg) { Get-History -c $MaximumHistoryCount | out-string -stream | select-string $arg }