This is strange.
I know that the tab is intended to complete the command in PowerShell ISE and so well. But it will also mix up the editing area.
Do it:
File> New ( Untitled1.ps1opens)
Click the tab (everything is fine, you will get the indent)
enter #(comment) and click the tab after it. Expected: you can get indents after the hash actual: hashes are replaced with $PSVersionTableor regardless of the command line in the history! (tab and circle Shift-tab)
Does this mean that nobody uses tabs in comments in PowerShell scripts, or that nobody uses comments in PowerShell scripts?
Is it possible to disable this behavior anywhere?
In addition, the behavior seems inconsistent. If I, for example, type ##, sometimes the tab does not complete the completion (it also does not enter the tab).
Can others reproduce this?

System: Windows 8.1 Pro PowerShell ISE
source
share