Does anybody know if there's a way in VS Code to tell the HTML and Markdown editors what the "root" of the site is?
I have a project where the web root lives under /site rather than / in the project, but the HTML and Markdown editors assume the root of the project == the root of the site. Short of opening just the site folder, is there a way to tell the editors where to look when doing Intellisense for links and to resolve static content in the Markdown preview?
Gotta say, VS Code and LSP have raised the bar for the baseline developer experience for all IDEs. Recently I installed an extension for shell scripts and with LSP support for the first time I have IDE support for shell scripting. It has all of the core IDE features that I would expect.
Data Wrangler is a new Microsoft VScode extension for data exploratory analysis. It supports Python 🐍 and Pandas 🐼 DataFrame objects and is integrated into VScode Jupyter Notebooks. Here are some of the functionalities of Data Wrangler:
✅ Data review
✅ Column filtering
✅ Summary statistics
✅ Data cleaning and transformation
✅ Hadeling missing values
✅ Creating new fields
The Microsoft #devskim project looks great, but it could use some #dev activity.
There is a great opportunity to improve the #vscode plugin or the #cli tool or to improve it's current default ruleset. You can use this tool for #security in your code, or common best practices.
Will you help me popularize it's usage? For me it's a serious contestant for the sluggish #sonarcube if it gets a bit more love 🩷
So over the past year I have been using #vscode for my #rstats and #python work. my workplace is trying to move to a unified IDE, and vscode allows remote access and WSL integration for free. However, so far it fails to spark joy in me like #RStudio (despite lack of #vim mode) and #PyCharm do. Everything feels clunky, and subpar. The "intelligent" and linting things are also quite broken in R... Has there been extensions that fundamentally change the vscode experience that I should be trying?
In the past few months, I created a bunch of Docker 🐳 tutorials covering random topics, from a fun setting for a Python 🐍 environment on the CLI to advanced topics such as multi-stage builds 🏗️. I organized all the tutorials under one folder, and I plan to keep updating this folder with future-related ones 😎.
Currently on my Docker tutorial TODO list:
➡️ Docker ENTRYPOINT vs CMD
➡️ Docker multi-architecture build
I feel like the only complaint I have of #Kate, is that I use text editors like Kate/#VSCode a lot for searching certain keywords - this is a common use case I'm sure.
On VS Code this is easy, on Kate it can/should be too... except the arrows to go to the next or earlier iteration keeps moving when it reaches the very first iteration or very last iteration. It's such a little thing but genuinely frustrating - only bcos it is a very common use case when you're using a text editor like it.
I just turned off the "minimap" feature of #VSCode after realizing I've had it on for like a decade without ever looking at it. Is it useful somehow, or just a gimmick?
Getting started with the Dev Containers extension 🚀👇🏼
The Dev Containers extension is the main reason I moved to VScode, as it provides a native and seamless integration of Docker 🐳. I started to work on a sequence of tutorials focusing on the VScode Dev Containers extension. The first tutorial on the sequence focuses on getting started with the Dev Containers extension;
🧏 People who code have a tendency to spend a lot of time in various IDEs (Integrated Development Environments). They can be as simple as a text editor or as complex as a full-blown development environment. In this post, I'll go through my two go-to IDE's, RStudio and VScode, and why I switch between them rather than sticking to a single one. ---
Trying out #VSCodium it's a fork of VSCode's source code, it's #FLOSS and comes without data collection and other proprietary code from Microsoft. It's avaible for Windows, Linux and MacOS :3
So far it's pretty great, it gives you a guide on how to transfer your #VSCode settings, extensions and Co. and also let's u use VSCode's Extension Marketplace if you prefer it over the #opensource one. Only thing which I miss is a way to sync 🥲, but thats fine.
Looking at the release notes, and It's absoluetely wild how much me and @charlieegan3 managed to get done in just 2 weeks, and all without neglecting our other responsibilities.. 😄
#Regal v0.21.0 is out now, and if you do any work at all with #OPA and #Rego, this release — together with the latest OPA #VSCode extension also released today — takes the Rego development experience to the next level. Try it out and let me know what you think! Changelog and downloads here:
I am extraordinarily annoyed by the fact that #Copilot appears to be enabled by default now in #VSCode and I can't find any way to turn it off. #dotnet#csharp
@boo_@andros I didn’t foresee anyone turning Google’s #Chrome browser #JavaScript engine V8 (2008) into the server (#NodeJs, 2009) and desktop (#ElectronJs, 2013) runtimes that ate the world, but here we are.
And Electron was originally developed for #GitHub’s #Atom text editor (2008) before they were acquired by #Microsoft in 2018, subsequently discontinued in favor of #VSCode in 2022.
Don’t tell me what you can’t see happening if you don’t remember what already did