Here’s something Use CTRL + to zoom in Use CTRL - to zoom out Edit: VScode can sometimes auto adjust so watch out for that, But it sometimes it fine, so just remember those commands and you should be fine. Happy coding. Answer from slightplyz on forum.freecodecamp.org
🌐
Reddit
reddit.com › r/vscode › visual studio code blurry
r/vscode on Reddit: Visual Studio Code blurry
October 31, 2018 - Try changing your display resolution. That should fix it · Reply · reply · Brnchy · • · • · Does the blur stay in the sameplace when you drag the screen smaller? Reply · reply · [deleted] • · • · Try going into properties on the exe file and going to the compatibility tab and playing with the dpi settings there · Reply · reply · Top 2% Rank by size · r/vscode • ·
🌐
GitHub
github.com › microsoft › vscode › issues › 9432
Poor performance on large resolution · Issue #9432 · microsoft/vscode
July 18, 2016 - Version: VSCode Insiders. Latest OS X I have a secondary monitor plugged into my MacBook pro which has 3840 x 2160 pixels. I have my resolution set to 2560 x 1440. When I resize vscode to use the f...
Author   OliverJAsh
🌐
Stack Overflow
stackoverflow.com › questions › 78045735 › vs-code-screen-size
VS Code Screen Size - Stack Overflow
The fact that VSCode is used for coding does not make it so. In most applications, Ctrl+mouse-wheel or Ctrl+= and Ctrl+- will zoom in and out to fit content. ... What do you call the screen size? To me it sounds like the monitor resolution, but then your question makes no sense.
🌐
GitHub
github.com › microsoft › vscode › issues › 90650
Incorrect window dimensions/rendering after screen resolution change · Issue #90650 · microsoft/vscode
February 14, 2020 - Issue Type: Bug When launched VS Code renders correctly on either display, but after a screen resolution change the dimensions appear to be off by 4px on all sides. VS Code is maximized. Scenario 1: Launch with single screen, 3000x2000 2...
Author   johnpedersen-freightways
🌐
Visual Studio Code
code.visualstudio.com › docs › sourcecontrol › merge-conflicts
Resolve merge conflicts in VS Code
November 3, 2021 - Learn how to resolve Git merge conflicts in VS Code using inline editor actions, the 3-way merge editor, and AI-assisted resolution.
Find elsewhere
🌐
Visual Studio Code
code.visualstudio.com › docs › sourcecontrol › overview
Source Control in VS Code
November 3, 2021 - Learn how to use VS Code's integrated Git source control features like staging, committing, branching, merge conflict resolution, and GitHub integration.
🌐
GitHub
github.com › microsoft › vscode › issues › 162309
Manual resolution is still appearing as conflict? · Issue #162309 · microsoft/vscode
September 29, 2022 - Here in this case I see a "manual resolution" as one of the conflicts, but I am a bit confused: if the conflict was automatically manually resolved, why is it still appearing as conflict? merge.jso...
Author   bpasero
🌐
Visual Studio Code
code.visualstudio.com › docs › getstarted › settings
User and workspace settings
February 6, 2025 - How to modify Visual Studio Code User and Workspace Settings.
🌐
GitHub
github.com › microsoft › vscode › issues › 135492
Ubuntu 21.10: The whole vscode application looks blur under 200% DPI scaling · Issue #135492 · microsoft/vscode
October 20, 2021 - Open vscode · Update: Disable "Fractional Scaling" and then the problem solved. But if other users are using 125%, 150% or 175% scaling, this problem might not avoid? 👍React with 👍2dieseltravis and Melebius · deepak1556 · No labels ...
Author   Demonese
🌐
Opt Node
optnode.com › home › guides › solving import resolution problems in visual studio code for python users: a comprehensive guide
Solving Import Resolution Problems in Visual Studio Code for Python Users: A Comprehensive Guide - Opt Node
August 22, 2025 - Import resolution issues in Visual Studio Code can be a real headache for Python developers. Luckily, you can solve many of these problems by ensuring the Python interpreter is set correctly, installing necessary packages, and configuring the workspace to recognize the modules.
🌐
GitHub
github.com › microsoft › vscode › issues › 95523
VSC loses resolution while I'm working · Issue #95523 · microsoft/vscode
April 17, 2020 - I'm having a strange problem where my code becomes barely visible while I'm working. I've been having this issue for more than a month already. I've tried updating the graphic drive...
Author   ygspasov
🌐
GitHub
github.com › microsoft › vscode › issues › 84164
vs code won't size right on multiple monitors · Issue #84164 · microsoft/vscode
November 7, 2019 - I have 3 monitors. a Surface Book 2 on the bottom, with 2 monitors above the book (left and right). The external monitors are 1920x1080. If I open a file on the Surface monitor, it will fit. I can resize it to be half the height of the m...
Author   robinsh
🌐
Reddit
reddit.com › r/vscode › confused about git conflict management in the ui
r/vscode on Reddit: Confused about Git conflict management in the UI
January 24, 2025 -

If i merge, and there's conflicts in a file, I often end up in a weird situation that seems almost bugged. But maybe I'm doing it wrong.

So, I'll merge, and I click the file in source control, which opens it. I can see the changes, and say I hit 'accept current'. The red/green diff highlight disappears, but the file still has a ! and says there's conflicts. If I close the file, it says it has unhandled conflicts.. the only solution then is to hit 'open in merge editor'. So, #1 issue is, why isn't it resolved at this point??

Anyway, going into the merge editor, I see the diff area but its entirely red, and it says 'manual resolution' or 'reset to base'. Manual resolution is not clickable, so I assume it's wanting me to resolve it manually, but it's already merged correctly from when I hit 'accept current'. I can't click 'Complete Merge' at this point, because it's still wanting me to fix the red area.

Sometimes at this point I can put a space and then delete the space, and it accepts that i've done a manual edit and lets me complete the merge. But right now as I'm writing this post and testing it, it's not letting me.

What is going on? This happens constantly. And before anyone asks, no there's no other area in the file that has a conflict - I'm testing right now on a small .gitignore file.

🌐
GitHub
github.com › microsoft › vscode › issues › 45492
Large portions of the window not repainting on high DPI/resolution displays · Issue #45492 · microsoft/vscode
March 10, 2018 - Issue Type: Bug When VS Code sits open for a while, say in the background or after an unmeasured time of just sitting around, large portions of the window appear to not repaint. This also occurs with more "complicated" views, such as the...
Author   BytewaveMLP
🌐
GitHub
github.com › microsoft › vscode › issues › 75111
Sluggish User Interface on High-Resolution Screens · Issue #75111 · microsoft/vscode
June 7, 2019 - Issue Type: Performance Issue Hey there, I often experience sluggish and laggy UI when working with VS Code, e.g. clicking on tabs, activity bar icons, menus, etc. Is this related to certain machin...