{"id":7491,"date":"2015-03-04T00:01:00","date_gmt":"2015-03-04T00:01:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/heyscriptingguy\/2015\/03\/04\/dont-script-edit-powershell-command-history\/"},"modified":"2019-02-18T10:30:24","modified_gmt":"2019-02-18T17:30:24","slug":"dont-script-edit-powershell-command-history","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/scripting\/dont-script-edit-powershell-command-history\/","title":{"rendered":"Don’t Script: Edit PowerShell Command History"},"content":{"rendered":"

Summary<\/b>: Microsoft Scripting Guy, Ed Wilson, talks about editing the Windows PowerShell command history.<\/span><\/p>\n

\"Hey, Hey, Scripting Guy! I liked your ideas in Avoid Scripting: Use PowerShell Command History<\/a>. My problem is that I seldom (if ever) type commands perfectly the first time—often, not even the second time. This means that I end up with a lot of junk in my command history. I wish there was a way to clean up the command history so it would be more usable. Is there?<\/p>\n

—AP<\/p>\n

\"Hey, Hello AP,<\/p>\n

Microsoft Scripting Guy, Ed Wilson, is here. This afternoon, I am listening to a Canadian rock group and sipping some pomegranate tea. Of course, pomegranate is not really a tea, and a pomegranate tea is actually an herbal fruit kind of concoction. But hey—it is still nice and refreshing, and it doesn’t have any caffeine in it. Along with chocolate biscotti, it makes a great way to work.<\/p>\n

AP, another great way to work is to use your Windows PowerShell command history. It is actually very flexible, and it is pretty easy to edit the history if you want to do so.<\/p>\n

Editing the Windows PowerShell command history is perhaps a misnomer. I cannot really edit the command history, but I can delete items from it and add items to it. I cannot edit an actual entry from the command history—well actually, I could, but I would need to export the history to a file, edit the file, and then import the history back in, which is a bit more work than I want to do. (If this was a scenario that I found myself doing on a regular basis, I could write a function to make it more doable.)<\/p>\n

How do I remove stuff from my Windows PowerShell command history? I use the Clear-History<\/b> cmdlet. I will admit that when I first saw this cmdlet, I thought that it…well…cleared all of my history from Windows PowerShell. And it will do that, of course. Here is an example:<\/p>\n

PS C:\\> Clear-History<\/p>\n

PS C:\\><\/p>\n

I type the command, and nothing returns. If I want to see a bit more information, I can use the standard –Verbose<\/b> Windows PowerShell parameter. This will tell me that the command is clearing my Windows PowerShell command history. This is shown here:<\/p>\n

PS C:\\> Clear-History -Verbose<\/p>\n

VERBOSE: Performing the operation "Clear-History" on target "This command will clear all the entries from the session history."<\/p>\n

As shown here, I can also use the –WhatIf<\/b> parameter if I am unsure that I want to remove all items:<\/p>\n

PS C:\\> Clear-History -WhatIf<\/p>\n

What if: Performing the operation "Clear-History" on target "This command will clear all the entries from the session history."<\/p>\n

But the cmdlet is more flexible than simply emptying my Windows PowerShell history. I could remove specific items from my Windows PowerShell history. Before I remove a specific item from the Windows PowerShell command history, I like to look at the command. I can do this by using the Get-History<\/b> cmdlet and specify a specific ID number. I then pipe the results to the Format-List<\/b> cmdlet so I can see more information than the standard output. Here is the standard output:<\/p>\n

PS C:\\> Get-History 67<\/p>\n

  Id CommandLine<\/p>\n

  —   ———–<\/p>\n

  67 srv<\/p>\n

Here is the more detailed output:<\/p>\n

PS C:\\> Get-History 67 | fl *<\/p>\n

Id                 : 67<\/p>\n

CommandLine        : srv<\/p>\n

ExecutionStatus    : Completed<\/p>\n

StartExecutionTime : 3\/2\/2015 3:15:36 PM<\/p>\n

EndExecutionTime   : 3\/2\/2015 3:15:36 PM<\/p>\n

Because a command completed (as did the previous command), it does not mean that it completed successfully. Here is what happens when I try to use the Invoke-History<\/b> cmdlet (r<\/b> is an alias) to execute the command:<\/p>\n

PS C:\\> r 67<\/p>\n

srv<\/p>\n

srv : The term 'srv' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.<\/p>\n

At line:1 char:1<\/p>\n

+ srv<\/p>\n

+ ~~~<\/p>\n

    + CategoryInfo          : ObjectNotFound: (srv:String) [], CommandNotFoundException<\/span><\/p>\n

    + FullyQualifiedErrorId : CommandNotFoundException<\/p>\n

Finding a specific command<\/h2>\n

So I have a command that doesn’t work in my Windows PowerShell command history. I can find all of these types of commands by using the Get-History<\/b> command and piping the results to the Where-Object<\/b> cmdlet. I already know that I have a property called CommandLine<\/b> that contains my commands. Here is the command I use to find the commands:<\/p>\n

PS C:\\> Get-History | where commandline -eq 'srv'<\/p>\n

  Id CommandLine<\/p>\n

  —   ———–<\/p>\n

  67 srv<\/p>\n

  78 srv<\/p>\n

  81 srv<\/p>\n

Removing the bad commands from history<\/h2>\n

I thought I might need to pipe the results of my Get-History<\/b> cmdlet to the Clear-History<\/b> cmdet. But as it turns out, I don’t need to do that. I can use Clear-History<\/b> to search for and remove my bad command:<\/p>\n

Clear-History -CommandLine 'srv'<\/p>\n

Sweet…no errors. Then I decide to use the Up arrow to recall my previous Get-History<\/b> command. Bummer. I still have a couple of entries remaining:<\/p>\n

PS C:\\> Get-History | where commandline -eq 'srv'<\/p>\n

  Id CommandLine<\/p>\n

  —   ———–<\/p>\n

  78 srv<\/p>\n

  81 srv<\/p>\n

I remember to use the count. I see that there are two instances of the bad command still in history, so I use the Up arrow and add the count. Here is my command:<\/p>\n

Clear-History -CommandLine 'srv' -Count 2<\/p>\n

Now when I use the Get-History<\/b> command, nothing appears.<\/p>\n

These commands and their associated output are shown in the following image:<\/p>\n

\"Image<\/a><\/p>\n

AP, that is all there is to editing the Windows PowerShell command history. Script Without Scripting Week will continue tomorrow when I will talk about using code snippets.<\/p>\n

I invite you to follow me on Twitter<\/a> and Facebook<\/a>. If you have any questions, send email to me at scripter@microsoft.com<\/a>, or post your questions on the Official Scripting Guys Forum<\/a>. See you tomorrow. Until then, peace.<\/p>\n

Ed Wilson, Microsoft Scripting Guy<\/b> <\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about editing the Windows PowerShell command history.  Hey, Scripting Guy! I liked your ideas in Avoid Scripting: Use PowerShell Command History. My problem is that I seldom (if ever) type commands perfectly the first time—often, not even the second time. This means that I end up with a […]<\/p>\n","protected":false},"author":596,"featured_media":87096,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[51,3,4,45],"class_list":["post-7491","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scripting","tag-getting-started","tag-scripting-guy","tag-scripting-techniques","tag-windows-powershell"],"acf":[],"blog_post_summary":"

Summary: Microsoft Scripting Guy, Ed Wilson, talks about editing the Windows PowerShell command history.  Hey, Scripting Guy! I liked your ideas in Avoid Scripting: Use PowerShell Command History. My problem is that I seldom (if ever) type commands perfectly the first time—often, not even the second time. This means that I end up with a […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/7491","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/users\/596"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/comments?post=7491"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/posts\/7491\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media\/87096"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/media?parent=7491"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/categories?post=7491"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/scripting\/wp-json\/wp\/v2\/tags?post=7491"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}