N3Cr0@lemmy.world to linuxmemes@lemmy.world · 10 days agoVim > VSCodelemmy.worldexternal-linkmessage-square154fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkVim > VSCodelemmy.worldN3Cr0@lemmy.world to linuxmemes@lemmy.world · 10 days agomessage-square154fedilink
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up0·edit-29 days ago Is there a stable way to use closed extensions (like the MS Python one) with vscodium by now? Yes. Use this config edit.. Everything works fine.
minus-squareFooBarrington@lemmy.worldlinkfedilinkarrow-up0·9 days agoHm, people in the GitHub issue are still complaining that it doesn’t work. Does it work fine for you? https://github.com/VSCodium/vscodium/discussions/1641
minus-squarepinball_wizard@lemmy.ziplinkfedilinkarrow-up0·9 days agoI’ve never had any issues with any VSCode plugin failing in VSCodium. But I’m not a PyLance user.
minus-squareFooBarrington@lemmy.worldlinkfedilinkarrow-up0·9 days agoYour experience with other extensions sadly doesn’t mean much for Pylance. It specifically has DRM implemented to prevent vscodium from loading it, just like some other MS extensions. That’s why I’m asking.
Yes. Use this config edit.. Everything works fine.
Hm, people in the GitHub issue are still complaining that it doesn’t work. Does it work fine for you?
https://github.com/VSCodium/vscodium/discussions/1641
I’ve never had any issues with any VSCode plugin failing in VSCodium.
But I’m not a PyLance user.
Your experience with other extensions sadly doesn’t mean much for Pylance. It specifically has DRM implemented to prevent vscodium from loading it, just like some other MS extensions. That’s why I’m asking.