A pop-history Cmdl

Hello all together,
Maybe a good note, when you startup a PS script with a lot of input for
instance "Yes" or "No" or "add or delete", etc., etc. and after completion
you need to start again for an other client, you must back and back by the up
arrow, because all the input from the shell is in the history. When there is
a Cmdl pop-history that delete the last history that I can place after the
use of the data from read-host. Now I close every time Windows PowerShell and
start it again with an empty history.
I hope that maybe other Windows PowerShell users who have the same
experience with big forms give a good response at this item.
Cheers Ger

--
I thank you in advance for your reaction.
Ger

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/communities...ows.powershell

"Ger F." <GerF@xxxxxx> wrote in message
news:9A939CEA-793B-4D11-A67D-7BBB2EDF741F@xxxxxx

See if this blog entry helps.

Perserving Command History Across Sessions
http://blogs.msdn.com/powershell/arc...01/653194.aspx

--
Jon

Try Invoke-History or its alias 'ihy'

Quoting from (help ihy):

"If you type characters, Invoke-History matches the most recent commands first. If you omit this parameter, Invoke-History runs the last (mostrecent) command. The parameter name ("-id") is optional. To find the ID number of a command, use Get-History."

You would only need to type ihy to run the script again.

--
Kiron