danhab99@programming.dev to Programmer Humor@programming.dev · 2 years agoemacsprogramming.devimagemessage-square88fedilinkarrow-up1642arrow-down179
arrow-up1563arrow-down1imageemacsprogramming.devdanhab99@programming.dev to Programmer Humor@programming.dev · 2 years agomessage-square88fedilink
minus-squareEthab83@sh.itjust.workslinkfedilinkarrow-up18arrow-down2·2 years agoIt is, but the lack of official Microsoft extensions makes life a little harder
minus-squareHurglet@lemmy.basedcount.comlinkfedilinkarrow-up19·2 years agoYou can change the extension repository to the official one. I don’t need it tho, I only need Pyright, Python and the catppuccin theme
minus-squaretostiman@sh.itjust.workslinkfedilinkarrow-up5·2 years agoSome MS addons still don’t work if you do that, last time I tried
minus-squareHurglet@lemmy.basedcount.comlinkfedilinkarrow-up3·2 years agoThat’s weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn’t actively break addon. Unless they check if they’re running inside of the actual MS VSCode, which could explain why they aren’t working
minus-squaretostiman@sh.itjust.workslinkfedilinkarrow-up11·2 years agoIIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binaries
minus-squareskarn@discuss.tchncs.delinkfedilinkarrow-up1·2 years agoYou can get e.g. pylance to work if you trick it: https://github.com/VSCodium/vscodium/issues/1640 So, at least in that instance, it’s just Microsoft being a little petty.
minus-squareskilltheamps@feddit.delinkfedilinkarrow-up3·2 years agoThe most unfortunate of which for me is remote development. So convenient, nothing compares :(
It is, but the lack of official Microsoft extensions makes life a little harder
You can change the extension repository to the official one.
I don’t need it tho, I only need Pyright, Python and the catppuccin theme
Some MS addons still don’t work if you do that, last time I tried
That’s weird, AFAIk VSCodium only strips telemetry and changes branding. It shouldn’t actively break addon.
Unless they check if they’re running inside of the actual MS VSCode, which could explain why they aren’t working
IIRC VSCode contains some proprietary, closed source binaries and VSCodium does not. So maybe the MS addons need those binaries
You can get e.g. pylance to work if you trick it:
https://github.com/VSCodium/vscodium/issues/1640
So, at least in that instance, it’s just Microsoft being a little petty.
The most unfortunate of which for me is remote development. So convenient, nothing compares :(