Jason Shirk

@bitcrazed linked to the issue that caused the problem. The fix is in this PR: https://github.com/lzybkr/PSReadLine/pull/771

I'll try to release another beta to the PowerShell Gallery before the end of the year, but I don't know about Windows (I don't work on Windows). @SteveL-MSFT owns the...

I see. It is surprising to me that ScriptAnalyzer walks the root ScriptBlockAst for me, I would have thought the rule decides if it needs to analyze nested script blocks.

Documentation could be improved, this [document](https://github.com/PowerShell/PSScriptAnalyzer/blob/development/ScriptRuleDocumentation.md) says nothing on the matter. In fact, the only examples have the same flaw - they accept a `ScriptBlockAst` and pass `$true` when calling...

It's probably not a big deal either way, but my thoughts before opening the issue: * Rust decided creation flags were important enough to add an api * `duct` already...

If you run the same program from `cmd.exe`, I'm guessing you'll get a popup about a dll that can't be found. Assuming so, the cause is this line of [code](https://github.com/PowerShell/PowerShell-Native/blob/d4acbd519d1c77e07abc894db42853055ef65f55/src/powershell-native/nativemsh/pwrshcommon/pwrshcommon.cpp#L1525)....

Interesting approach. I'm not interested in taking a dependency on `System.Windows.Forms` - I used it for clipboard support but removed the dependency to work as a `netstandard2` assembly. I haven't...

One other thing - ideally we can fix this on every platform, not just Windows. The heuristic approach should work cross-platform, but I'm open to more reliable approaches like yours...

@MaximoTrinidad - PSReadLine has always worked this way and it is a little different than without PSReadLine. It wasn't much of a problem because Ctrl+v is preferred - it is...

As I said, Ctrl+v works in Windows PowerShell, but you need PSReadLine 2.0 (no official builds available yet) for PowerShell Core. And I fully understand the problem, you don't need...