Windows PowerShell ISE: Caret and View do not jump to text being undone/redone
Votes from Connect: 18
Original Date Submitted: 6/21/2013 12:49:43 AM
Site Name: PowerShell
Feedback ID: 790586
Frequency: Always Happens
Regression: I do not know if this issue existed previously
In the PS ISE v3 Script Pane, if you use the undo or redo commands (Ctrl+Z and Ctrl+Y respectively), the caret does not jump to the text being undone/redone, and the view does not scroll to the text being undone/redone either. So if the text being changed is outside of the visible area, you don't know what changes are being undone/redone. This is a real problem when you have scripts that are hundreds or thousands of lines long.
Product Studio item created by Connect Synchronizer due to creation of feedback ID 790586 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=790586).
Open a new file in the Script Pane and type in a bunch of text so that there is more text than can be viewed on the screen at a time. Change some text at the top of the file, save the file, then scroll to the bottom of the file and perform an Undo (Ctrl+Z). Notice that the dirty flag appears on the file's tab so you can see that it was changed, but you cannot see the text that was undone.
When you perform and Undo or Redo, the file should scroll so that the text being undone/redone is visible, and the caret should also jump to the text being undone/redone.
Internal BugId: 4263
Bernhard Bäumle commented
This problem still exists (PSVersion 5.1.14393.3383, Jan 2020).
A small fix (to move the Caret and View to the text being undone/redone) would be very much appreciated!!!
Eddie Kumar commented
Did this ever get fixed?
This is crucial as number of times this caught me, when I unintentionally performed undo operation on more than desired lines as it doesn't scroll the screen to show where (in script) it is performing the undo (this is not acceptable).
There are lots of reasons why lots of people like to code within ISE (rather than using another heavy IDE), therefore it will be very much appreciated if Microsoft fixes this major bug in PowerShell ISE.
As tiny of a change this would be with almost no conceivable downside, the amount of time it would save on scripts with hundreds or thousands of lines is huge.