With Windows PowerShell, complains about missing xclip the first it's used if StrictMode is in effect about clipboardtext HOT 2 CLOSED

Fix tested with Windows PowerShell 5.1 and PowerShell Core 6.1.

Good job!

from clipboardtext.

Good find, and thanks for the detailed pointers - just published v0.1.7 with a fix.

As an aside:

Modules that don't have ScriptsToProcess entries won't be affected, but I expect that many a script will break if you spring a global Set-StrictMode -Version Latest on it (unless these scripts all manage their own strict mode).

There is a - languishing - RFC that proposes introduction of a lexical strict mode, that would avoid such problems - see https://github.com/PowerShell/PowerShell-RFC/blob/master/1-Draft/RFC0003-Lexical-Strict-Mode.md

from clipboardtext.