Since they upgraded their glibc requirements for remote servers from 2.26 to 2.28, I can’t use it to work on important legacy servers. So I am stuck with a version 6 months old. I wish I could’ve used the newer version
From a cursory glance, it looks like Amazon Linux 2 did not meet the minimum system requirements for a new version of VScode. In this situation, is only one party at fault? Is VScode to blame for not ensuring their software works with as many machines as possible, or is it Amazon Linux’s issue for not bundling updated drivers? Or is it a bit of both?
Knowingly releasing the update that affects so many developers without informing the user that it may break their workflow until after you’ve already updated is on vscode. You can scroll up that thread to see people raising issues at least a week before release
You may not find a use for it, and neither do I in my workflow. But think about accessibility - it might enable some users to perform tasks the find physically difficult using just their voice.
Or, you can go get a beer or a [slice of] pizza, and call out to vscode from across the room to build your app or start a server or something.
Indeed - users that need accessable features should not rely on each piece of software they use to supply them. But even as a one-off feature, it is a good thing to have IMO, as it will certainly expose APIs and hooks in vscode for other accessibility software to utilize.
Now I’m hoping that the devs add the ability to use a different font for comments and/or docstrings.
I have had mine set up to use a different font for comments for quite a while, but I don’t recall how I set it up that way. If I remember, next time I’m in front of my computer, I’ll see if so can figure it out and respond again.
It’s probably the CSS extension. I keep meaning to try it but always forget! Now that I’ve figured out a workaround for VSCode not showing the correct Iosevka font weight, I’ll give the CSS extension a go. Thank you for the sort of reminder!
or build one yourself? I’ve never built an extension for VS Code. May be worthwhile, if it isn’t too difficult. For now, I’m just using big comments to deliminate my functions. Encourages good comment habits as a side-effect, so I’m not too upset.
I’m really impressed that floating editor windows are available in the Insider builds, I’m definitely going to give it a try, I’ve been waiting for that for what now seems forever.
Floating editor windows exploration We have started to explore how to pull editors out of the workbench window into their own windows. This feature is our highest upvoted feature request and we plan to have a first working version for our Insiders users to play with in October.
Seems like detachable panels, if you scroll all the way down on the article you’ll see a video of it working. So excited for this feature. I’ve in the past did the whole “two intances sharing workspace” but as you said, it such overkill.
vscode
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.