Skip to content
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

VSCode Editor is empty for all files #11715

Closed
alanwright opened this issue Sep 8, 2016 · 9 comments · Fixed by #11718
Closed

VSCode Editor is empty for all files #11715

alanwright opened this issue Sep 8, 2016 · 9 comments · Fixed by #11718
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release important Issue identified as high-priority verified Verification succeeded
Milestone

Comments

@alanwright
Copy link

alanwright commented Sep 8, 2016

  • VSCode Version: 1.5.0
  • OS Version: Windows 10 Enterprise (Build 10586.545)

Microsoft internal alias: alanwri

Steps to Reproduce:

  1. Open VSCode
  2. When opening any file, nothing shows up in the text editor
    Happens for all types of files, VSCode is unusable. Tried fresh uninstall, and install from vscode website, still repros. No idea what to do. Feel free to ping me internally and I can share my screen, etc.

image

@alanwright
Copy link
Author

Uninstalled all my extensions and restarted. Still no fix

@Tyriar
Copy link
Member

Tyriar commented Sep 8, 2016

This is happening due to a change that makes the editor respect "editor.fontSize": 0. The fix is to remove that setting value. To do that you can open your settings, select all, cut and save.

  1. ctrl/cmd+a
  2. ctrl/cmd+x
  3. ctrl/cmd+s

Your old settings file can then be pasted into the editor.

If the above is not possible for whatever reason (your keybindings are unset or something?) then the settings.json file can be accessed in another editor at:

  • Windows: %APPDATA%/Code/User/settings.json
  • Linux: ~/.config/Code/User/settings.json
  • Mac: ~/Library/Application Support/Code/User/settings.json

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority editor candidate Issue identified as probable candidate for fixing in the next release labels Sep 8, 2016
Tyriar added a commit that referenced this issue Sep 8, 2016
toFloat only falls back to the default when the value is NaN, so an
explicit check for 0 is required.

Fixes #11715
@alanwright
Copy link
Author

This fixed it, thank you!

Tyriar added a commit that referenced this issue Sep 8, 2016
toFloat only falls back to the default when the value is NaN, so an
explicit check for 0 is required.

Fixes #11715
@Tyriar Tyriar added this to the August 2016 milestone Sep 8, 2016
@kieferrm
Copy link
Member

kieferrm commented Sep 8, 2016

We released 1.5.1 as recovery build.

@codinronan
Copy link

That is really impressive how quickly you guys pushed that out.

@deviprsd
Copy link

deviprsd commented Sep 9, 2016

Woah, way too fast. Impressive.

@andrew-locklair
Copy link

Kudos, VSCode team. Amazing job.

@RobertoMalatesta
Copy link

Astonished by the level of care and support your (really, really) distinguished team gives to this product.

--R

@vip3rousmango
Copy link

Ty for the quick fix! From one dev to another, it's really appreciated and why I continue to love using VS Code.

@Tyriar Tyriar added the verified Verification succeeded label Sep 29, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants