-
Notifications
You must be signed in to change notification settings - Fork 30k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrated terminal width too narrow #86425
Comments
(Experimental duplicate detection) |
Can you share your settings? |
Absolutely. My Code settings are synced to this gist https://gist.github.com/Mellbourn/2cb4e0da308c4bb3b086d64370238de7 I have tested running VS Code Insiders without my VS Code settings, and the problem is still there, though not as pronounced. The width of the gap seems to vary with the font used. Fira Code is worst (widest gap). Then Menlo, and finally Cascadia Code is the least bad. But I have now discovered that the most important settings is |
I can confirm the same behavior on a brand new install of VSCode Insiders:
No extensions are installed and the renderer is set to either |
Copied over from #87153 (comment) Note that this depends on the renderer being used, the char width differs between dom and the others and we use the dom sizing to determine the size as it's the widest. Since renderers aren't changed much I guess we should do a resize to fix this up. This is blocked on an upstream API to pull char dimensions xtermjs/xterm.js#702 |
@Tyriar thanks for pointing out the external issue, which unfortunately doesn't seem to be making much progress. Is there anything we can do to mitigate that behavior when using Thanks. |
Lubuntu user here, same issue. |
There is no way I'm moving back to It's not perfect but I hope that helps until we really fix this issue. |
Can confirm :). This is getting hilarious 💯 |
can confirm bug
this is really ridiculous; however size 12 reduces that padding 😃 |
Bot wasn't happy with the latest Insiders release being on a separate branch. Fixed and retriggered. With luck, this will be automatically commented upon when Insiders goes back to 🤞 |
Should it be fixed now ?? it does not do what I was hoping for ...
|
@Tyriar Please tell me what to do
|
@Luxcium it's fixed when an insider's build goes out based on master. We're about to release stable though so that will be a few days to a week before that happens. It should work in the first 1.45.0-insider version. |
I would like to be more fluent (professional) at doing stuff at your level and to be able to understand the workflow of your projects to be able to contribute... Many times I have ideas but don't know how to implement them so I am not wasting your time by opening Feature Request issues... Very interesting to have access to such a nice workflow, even to a layman. I would like to be more up to the game I feel like playing soccer in my backyard, you are the ultimate football team players, the only difference is I can't have posters of my favorite players because it would be awkward to have a picture of you Daniel(@Tyriar) and Matt (@mjbvz) on the walls of my room... Probably I could have one of Anders Hejlsberg (@ahejlsberg) (Sorry for this unrelated comment but it's my way of telling you to keep up with your great work, you guys, and obviously also all the other team members I didn't mention for both VS CODE and TypeScript) |
hello @Tyriar it's annoying me again 😄I say annoying because I will probably still be sending a message that doesn't seem to be constructive... I understand that it is not helping you but I am just curious (also it's not a big deal for me in fact. But let's say its a 'deal' for me a small one but yeah ...) I did cmd+a to select the area of the terminal and did a screen capture:
|
@Luxcium can you share your settings? Works fine for me on Windows and Mac. |
This bug has been fixed in to the latest release of VS Code Insiders! @Mellbourn, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text Happy Coding! |
sorry (I feel bad now): {
// ...
"terminal.integrated.fontSize": 16,
"terminal.integrated.fontFamily": "Monofur NF,TerminessTTF NF",
"terminal.integrated.rendererType": "canvas",
"terminal.external.osxExec": "iterm2.app",
"terminal.integrated.copyOnSelection": true,
"terminal.integrated.cursorBlinking": true,
"terminal.integrated.cursorStyle": "line",
"terminal.integrated.enableBell": true,
"terminal.integrated.experimentalUseTitleEvent": true,
// "terminal.integrated.letterSpacing": 1,
"terminal.integrated.lineHeight": 1,
"terminal.integrated.scrollback": 10000,
"terminal.integrated.shell.osx": "/usr/local/bin/zsh",
"terminal.integrated.showExitAlert": true,
"code-runner.runInTerminal": true,
"terminal.integrated.shellArgs.osx": [
"-l",
"-i"
],
// ...
} |
@Luxcium thanks can repro. Not sure why you'd be sorry about finding a bug that I can now fix for all users? |
This bug has been fixed in to the latest release of VS Code Insiders! @Mellbourn, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text Happy Coding! |
/verified |
Steps to Reproduce:
This behaviour is new in 1.41.0-insider. 1.40.2 does not have the problem.
Does this issue occur when all extensions are disabled?: Yes
The text was updated successfully, but these errors were encountered: