Closed claysquareninety closed 5 years ago
Can you post your full .vscode/launch.json file (omit any sensitive information).
The setting already exists, it's called "rootDir", and it should default to "${workspaceFolder}" and should be present in your launch.json by default.
Yes, that's what it was set to:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
...
{
"type": "brightscript",
"request": "launch",
"name": "Home-express",
"host": "xxx.xxx.xxx.xxx",
"password": "xxxx",
"rootDir": "${workspaceFolder}",
"consoleOutput": "normal"
},
...
]
}
@claysquareninety I found the issue. It was actually happening for me too once I installed the plugin (instead of running from source). The line that registered the default configuration code was missing, it must have gotten dropped in one of the recent updates. I have already made the fix locally, and am prepping a new migration for today or tomorrow.
@claysquareninety version 1.3.1 of the extension resolved this issue. Try it out and let me know if that resolved the issue for you!
Works great, thanks!
On Thu, Dec 6, 2018 at 4:12 PM Bronley Plumb notifications@github.com wrote:
@claysquareninety https://github.com/claysquareninety version 1.3.1 of the extension resolved this issue. Try it out and let me know if that resolved the issue for you!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/TwitchBronBron/vscode-brightscript-language/issues/44#issuecomment-445048776, or mute the thread https://github.com/notifications/unsubscribe-auth/AdRtmZ6f-ysoOvrNSVAG67KmKjr8161mks5u2ZZLgaJpZM4Y52bg .
vs code EACCES: permission denied, mkdir '/out'
This occurs in 1.3.0 on macOS High Sierra (10.13.2) regardless of the owner and permissions of my workspace folder, existing 'out' directory, etc. Downgrading to vscode-brightscript-language@1.2.2 fixes this issue for me.
Now that I look at the error message again, is it trying to create my 'out' dir in '/'? Is there a new setting for this?