Attempt to fix issue with stepping in dbgr on Linux

[rkeithhill]

Fix #554

I'm not entirely sure about this fix but what I observed is that you could step once in the debugger on Linux but the second step did nothing until you pressed a key in the interactive session. That would wake up this code on the blocking ReadKey() and every time the token was set to cancel. The thought was to not block on ReadKey() but wake up every 100 mSecs and check if a key is available and also if cancellation was requested. What I don't know is if this would slow down fast typing. At 100 mSecs I wouldn't think so.

[daviwil]

Hmmm, I really hope ReadKey isn't the problem here. I used to use KeyAvailable but on Linux and macOS it causes all keys typed to be echoed to the terminal. Try using Get-Credential in the terminal and see if your password gets echoed back to you. I don't know that we'll be able to use this as the solution, I might need to investigate further.

[rkeithhill]

I'll try that tonight. BTW if there is another fix that is better, I'm all for it. We should probably look into what else is being blocked by the lock this code is residing in. Although blocking code in a lock, isn't that frowned up except maybe in producer/consumer scenarios?

[rkeithhill]

Well, Get-Credential is a little screwy: [cid:image001.png@01D34CA8.9B32A2C0] And the backspace key doesn’t work but ctrl+H will do backspace. Doh! Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 From: David Wilson<mailto:notifications@github.com> Sent: Monday, October 23, 2017 11:20 AM To: PowerShell/PowerShellEditorServices<mailto:PowerShellEditorServices@noreply.github.com> Cc: Keith Hill<mailto:r_keith_hill@hotmail.com>; Author<mailto:author@noreply.github.com> Subject: Re: [PowerShell/PowerShellEditorServices] Attempt to fix issue with stepping in dbgr on Linux (#557) Hmmm, I really hope ReadKey isn't the problem here. I used to use KeyAvailable but on Linux and macOS it causes all keys typed to be echoed to the terminal. Try using Get-Credential in the terminal and see if your password gets echoed back to you. I don't know that we'll be able to use this as the solution, I might need to investigate further. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FPowerShell%2FPowerShellEditorServices%2Fpull%2F557%23issuecomment-338732493&data=02%7C01%7Cr_keith_hill%40hotmail.com%7C0a9f8d7bb336461c816908d51a3a61b3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636443760397513663&sdata=cVrHD2b7jlpj0Lzc%2BBRcSJDZWJJBbqtXtXnXot4DPC4%3D&reserved=0>, or mute the thread<https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAE8AqA6VKESgasKGuEFg79qviXkg2WIdks5svMrmgaJpZM4QB2zy&data=02%7C01%7Cr_keith_hill%40hotmail.com%7C0a9f8d7bb336461c816908d51a3a61b3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636443760397513663&sdata=Lkw3znoOxX%2FJmoTZ1bw45yfx%2BsACAyhp9uVsP4ZZ%2FHg%3D&reserved=0>.

[rkeithhill]

This approach echos the password to the screen when executing Get-Credential and the backspace key doesn't work. Crud.