Psreadline: "Start-Process -NoNewWindow -FilePath PowerShell" and cursor

[Gungor-x]

PS version: 5.1.17763.592
PSReadline version: 2.0.0-beta2
os: 10.0.17763.1 (WinBuild.160101.0800)
PS file version: 10.0.17763.1 (WinBuild.160101.0800)
BufferWidth: 120
BufferHeight: 3000

---

---

(Turkish)
"Start-Process -NoNewWindow -FilePath PowerShell " sorunlu bir koddur. Çünkü bu komutu kullanırsanız imleç sabit kalmaz. Powershell'de bu komut girildiyse, komut yazılırken ve imleç yukarı ve aşağı hareket eder.

(English)
"Start-Process -NoNewWindow -FilePath PowerShell " is problemly code. Because if use this command then cursor is'nt stable. if this command been entered at the powershell, while command been write and cursor move up and down.

[lzybkr]

I've hit this before but never tracked down what is going on. Very annoying and hard to get out of without closing the window.

[msftrncs]

Start-Process -NoNewWindow starts an ADDITIONAL process and connects it to the same window, but it does not 'pause' the original process, so now they are both running in the same window at the same time, both are accepting input and producing output, but since PSReadLine forces the cursor to where it believes it should be, you see the cursor move around depending on which process successfully read the input first. Start-Process -NoNewWindow should only be used by non-interactive background processes.

[SeeminglyScience]

The two processes also take turns accepting input which makes it super fun to type exit.

I think this is expected behavior, even if it is very disorienting to run into. If you really want a new interactive session in the same window just type powershell or add -Wait. Either way I'm not sure what PSRL could do differently here.

[lzybkr]

I forgot to mention - when I've seen this, it was surprising, as in, not likely me being foolish. I likely hit Ctrl+c when running some script (probably a batch file, not PowerShell).

Maybe it doesn't come up often, but if there is a good solution, it would be helpful.

[Gungor-x]

Example ,"Start-Process -NoNewWindow cmd" . I expect that Powershell works at the background and cmd works at the foreground. Maybe the opposite. In reality, two program works same window at the foreground. I think, this is a problem that especially interactive processes.

[msftrncs]

If you want to run a task as a background process, you should consider Start-Job, or a more elaborate configuration for Start-Process. Start-Process is working much like spawn would. Unless you specify new stdin, stdout and stderr, the new process always inherits these from the parent process, which is effectively what you get when you use NoNewWindow.

[msftrncs]

Or consider Start-Process -WindowStyle Hidden