-
Updated
Aug 12, 2021 - TypeScript
ide
Here are 1,766 public repositories matching this topic...
Please confirm that this problem is VSCodium-specific
- This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.
Please confirm that the issue/resolution isn't already documented
- [ X ] I checked the Docs page and my issue is not mentioned there.
To Reproduce
Steps to reproduc
-
Updated
Aug 15, 2021
- Select theme with thick strip in line number block.
- Save and restart. Open some file. Нou see that the first characters of the lines are hidden under stripe.
- Open another file. All display properly.
- If you see carefully that the whole block with line numbers in the first case is shifted to the left.
First file
-
Updated
Apr 1, 2020 - TypeScript
Let's move the CI over to Github Actions!
-
Updated
Mar 20, 2018 - TypeScript
Describe the bug
Some devfiles have several commands that need to be executed in a precise order to succeed.
Some are named with prefixed numbers that help the user, but some others are not.
For instance:
- angular
- python-django
Che version
- latest
- nightly
- other: please spec
-
Updated
Aug 9, 2021 - PHP
-
Updated
Aug 14, 2021 - Python
-
Updated
Aug 16, 2021 - TypeScript
-
Updated
Jul 21, 2020 - Go
cc rust-lang/rls#1112
cc microsoft/language-server-protocol#376
This causes problems with displaying correct diagnostic span and code suggestion spans (here).
Community QA
-
Updated
Aug 16, 2021 - Lua
-
Updated
Jul 7, 2021 - C++
-
Updated
Dec 23, 2020 - Haskell
-
Updated
Aug 12, 2021
-
Updated
Jun 26, 2021 - Lua
-
Updated
Oct 3, 2020 - C++
Improve this page
Add a description, image, and links to the ide topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the ide topic, visit your repo's landing page and select "manage topics."



Feature Description:
The command
workspace:openConfigFilerequires a mapping in the plugin system to be able to be executable by vscode plugins. We should therefore add an appropriate mapping for `workbench.action.openWorkspace