{"id":10081,"date":"2006-07-01T01:37:00","date_gmt":"2006-07-01T01:37:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/powershell\/2006\/07\/01\/perserving-command-history-across-sessions\/"},"modified":"2019-02-18T13:21:35","modified_gmt":"2019-02-18T20:21:35","slug":"perserving-command-history-across-sessions","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/powershell\/perserving-command-history-across-sessions\/","title":{"rendered":"Perserving Command History Across Sessions"},"content":{"rendered":"

<Edited 7\/2\/2006 to add tags and Categories><\/p>\n

Ben Winzenz didn’t like the fact that Windows PowerShell did not maintain history lists between sessions (http:\/\/winzenz.blogspot.com\/2006\/06\/cool-mshpowershell-tidbit.html<\/a>) .   We hear you Ben.  Back to my least favorite phrase, “to ship is to choose”.  That said, we try to give you in the community the power to do that which we cannot.  Here is some code that you can put in your profile file that defines a function BYE which saves off your sessions history into a History.CSV file in your home directory and then adds that to your history when you startup the next session.  You get to control how much of the history you want (up to 32KB-1) but I just do 1KBs worth.<\/p>\n

$MaximumHistoryCount = 1KB<\/font><\/p>\n

if (!(Test-Path ~\\PowerShell -PathType Container))
{   New-Item ~\\PowerShell -ItemType Directory
}<\/font><\/p>\n

function bye
{   Get-History -Count 1KB |Export-CSV ~\\PowerShell\\history.csv
    exit
}<\/font><\/p>\n

if (Test-path ~\\PowerShell\\History.csv)
{   Import-CSV ~\\PowerShell\\History.csv |Add-History
}
<\/font><\/p>\n

I was going to put comments in the code but thought I would test out my assertion that VERBOSITY produces self-documenting scripts.  I think it does but you can let me know one way or the other.<\/p>\n

So add this to your startup and then do a session, type BYE instead of EXIT and then start a new session and do a Get-History.   You’ll see a bunch of commands already in your list.  <\/p>\n

Now lets have a little fun with History, do what I instructed above and get into your new session.  Now do a Get-History and pipe it to Get-Member:<\/p>\n

PS> Get-History |Get-Member -MemberType Property
   TypeName: Microsoft.PowerShell.Commands.HistoryInfo<\/font><\/p>\n

Name               MemberType Definition
—-               ———- ———-
CommandLine        Property   System.String CommandLine {get;}
EndExecutionTime<\/font><\/strong>   Property   System.DateTime EndExecutionTime {get;}
ExecutionStatus    Property   System.Management.Automation.Runspaces.Pip…
Id                 Property   System.Int64 Id {get;}
StartExecutionTime<\/strong><\/font> Property   System.DateTime StartExecutionTime {get;}<\/font><\/p>\n

This means that you can find out when something was executed (e.g. which session it happened in) using the following command:<\/p>\n

PS> ghy |ft id,endexecutiontime,commandline -auto<\/font><\/p>\n

 Id EndExecutionTime      CommandLine
 — —————-      ———–
612 6\/29\/2006 5:39:34 AM  gcm export-csv |fl *
613 6\/30\/2006 6:51:16 PM  ipconfig
614 6\/30\/2006 8:51:38 PM  cd C:\\kits
…<\/font><\/p>\n

Enjoy!
Jeffrey P. Snover
Windows PowerShell Architect<\/p>\n

PSMDTAG:FAQ: How do I perserve command history across sessions?<\/p>\n

PSMDTAG:FAQ:  Can I run an exit script?<\/p>\n

PSMDTAG:ENVIRONMENT: History<\/p>\n

PSMDTAG:SHELL: shutdown, startup, exitScript<\/p>\n","protected":false},"excerpt":{"rendered":"

<Edited 7\/2\/2006 to add tags and Categories> Ben Winzenz didn’t like the fact that Windows PowerShell did not maintain history lists between sessions (http:\/\/winzenz.blogspot.com\/2006\/06\/cool-mshpowershell-tidbit.html) .   We hear you Ben.  Back to my least favorite phrase, “to ship is to choose”.  That said, we try to give you in the community the power to do that which […]<\/p>\n","protected":false},"author":600,"featured_media":13641,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[29,37,10,38,39,40,21],"class_list":["post-10081","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-powershell","tag-environment","tag-export-clixml","tag-faq","tag-get-history","tag-import-clixml","tag-sessions","tag-shell"],"acf":[],"blog_post_summary":"

<Edited 7\/2\/2006 to add tags and Categories> Ben Winzenz didn’t like the fact that Windows PowerShell did not maintain history lists between sessions (http:\/\/winzenz.blogspot.com\/2006\/06\/cool-mshpowershell-tidbit.html) .   We hear you Ben.  Back to my least favorite phrase, “to ship is to choose”.  That said, we try to give you in the community the power to do that which […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10081","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/users\/600"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/comments?post=10081"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/posts\/10081\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media\/13641"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/media?parent=10081"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/categories?post=10081"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/powershell\/wp-json\/wp\/v2\/tags?post=10081"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}