I'm using Visual Studio Code 1.33.1, running in Windows Subsystem for Linux (WSL)SL, and when i try Customize by installing support for Python, i get an error.
The message reads: "An unknown errror occurred. Please consult the log for more detials".
I don't know which log, or where it is, that this message mentions.
Can anyone help? - Thanks.
Note: i have reviewed the different suggestions presented as i tried to ask this question, but none were specific to Visual studio code.
Pengwin Version:
1.2.4.0
Windows Build:
10.0.17763 N/A Build 17763
Hello,
I have seen that others have problems installing plugins in VS code. Try running VS Code from / instead your home directory and try again to install the plugin.
Regards
Extensions have never worked great in Code on WSL. We've opened a couple issues on Code before about this. I think that's in part why they brought out the new Remote WSL extension.
hi Hayden:
thanks for the reply - as always.
Carlos Ramirez had replied the same.
and then last night, back at the house, i reinstalled VS Code, via Pengwin-Setup, b/c i noted v1.4 had just come out, and that install suggested removing it from WSL, installing the Windows version, and then use the extension.
i couldn’t figure out how to simply uninstall VS Code from WSL, however (again, being a WSL newbie —- maybe put uninstall capabilities in Setup?) . . . so uninstalled Pengwin from Windows Settings/Apps . . . and started over.
if you get chance to check out my direct e-mail to you, re. using the UltraEdit editor, would very much appreciate your thoughts.
10-4 for now,
thanks.
William W. Viergever
Viergever & Associates
Health Data Analysis / Systems Design & Development
2920 Arden Way Suite N
Sacramento, CA 95825
[email protected]william@viergever.net
www.viergever.nethttp://www.viergever.net/
On May 17, 2019, at 9:05 AM, Hayden <[email protected]notifications@github.com> wrote:
Extensions have never worked great in Code on WSL. We've opened a couple issues on Code before about this. I think that's in part why they brought out the new Remote WSL extension.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/WhitewaterFoundry/Pengwin/issues/460?email_source=notifications&email_token=ALB45AQZF743FD7REA7Q5BDPV3JVLA5CNFSM4HNQ6ZW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVVFPYQ#issuecomment-493508578, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALB45AWX2NRKH6P3MK7YVQLPV3JVLANCNFSM4HNQ6ZWQ.
Which extension do you want to install in VSCode?
hi Biswapriyo:
thanks for getting back to me.
i was trying to do the Python extension – shown on the initial splash-screen (under Customize / Tools and Languages).
note, however, i had noticed a new (1.34.0) version had come out that very day, and when i installed that (under Pengwin) it actually said to uninstall, install under Windows, and use the WSL extension . . . so i went that route.
appreciate all you guys’ replies.
William W. Viergever
Viergever & Associates
Health Data Analysis / Systems Design & Development
2920 Arden Way Suite N
Sacramento, CA 95825
[email protected]william@viergever.net
www.viergever.nethttp://www.viergever.net/
From: Biswapriyo Nath [mailto:[email protected]]
Sent: Wednesday, May 22, 2019 12:18 AM
To: WhitewaterFoundry/Pengwin
Cc: William W. Viergever; Author
Subject: Re: [WhitewaterFoundry/Pengwin] not technically a Pengwin bug, but am running VS Code under Pengwin and am getting errors trying to install support for Python (#460)
Which extension do you want to install in VSCode?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/WhitewaterFoundry/Pengwin/issues/460?email_source=notifications&email_token=ALB45AWOZ3MKQSIRD2KMK6TPWTXS7A5CNFSM4HNQ6ZW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV6EL7I#issuecomment-494683645, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ALB45AT43T6AOTFDZOQM26DPWTXS7ANCNFSM4HNQ6ZWQ.
I personally decided to dump the x version of Code for the native Windows Insiders build with the remote WSL extension as well. I suspect this is going to be a better developer experience going forward, but it's nice to know the X infrastructure is in place in case I need to use other GUI tools.