Closed pixelrebirth closed 6 years ago
@vors I wonder whether we should use "bypass" instead of "unrestricted"?
I agree that would be better, unrestricted was knee jerk of me-- bypass is more appropriate IMO
I agree.
Works perfect still, of course.
read-host doesnt however, but I think that is a limitation with sublime not being able to prompt correctly
OK. I'll be the noob who asks where to put the above? I've tried creating a Powershell directory in \users\me\appdata\roaming\sublime text 3\packages\powershell\Powershell.sublime-project and cloning into the packages directory only to see it deleted and editing the .sublime-project file both times the powershell directory gets removed on relaunch of Sublime Text. Clearly I'm doing it wrong.
C:\Users\me\AppData\Roaming\Sublime Text 3\Packages\PowerShell-master\Support\Powershell.sublime-build
Here is the fix for it:
{ "cmd": ["powershell.exe", "-noprofile", "-executionpolicy", "bypass", "$file"], "selector": "source.powershell" }
changed unrestricted to bypass based on comments below