Issue id
stringlengths 1
6
| Summary
stringlengths 1
277
| Created
stringdate 2015-11-13 16:34:23
2024-07-25 14:34:59
| Resolved
stringlengths 0
25
| Description
stringlengths 1
3.82k
| Resolution
stringclasses 4
values | Description_all
stringlengths 3
3.9k
| token_count
int16 6
1k
| Duplicates
listlengths 0
7
| Cluster
stringclasses 218
values | Num_duplicates
stringclasses 6
values | Has_duplicates
stringclasses 2
values |
|---|---|---|---|---|---|---|---|---|---|---|---|
172
|
Mac: Auto-update prevents to store settings of session
|
2015-11-19 09:00:23+00:00
|
2016-04-14 07:39:43+00:00
|
Whenever I install an update (prompted by VS Code) it doesn't open the same file I had opened before.
I think this is caused by a prompt process.exit() that leaves VS Code (or actually Chromium) no chance to persist the local storage to disk. It is reproducible by calling Lifecycle.quit() and from the done handler call process.exit().
Have to follow up with Electron to understand this better.
|
completed
|
Mac: Auto-update prevents to store settings of session Whenever I install an update (prompted by VS Code) it doesn't open the same file I had opened before.
I think this is caused by a prompt process.exit() that leaves VS Code (or actually Chromium) no chance to persist the local storage to disk. It is reproducible by calling Lifecycle.quit() and from the done handler call process.exit().
Have to follow up with Electron to understand this better.
| 115 |
[] |
0
|
False
|
|
170
|
"PreLaunchTask" is not finished before the launching starts
|
2015-11-19 08:54:06+00:00
|
2015-11-23 19:46:03+00:00
|
I have a simple TypeScript project, and I need to generate sourcemap before debugging.
I have a `tsc` task that does the job, and I set it as the `preLaunchTask` field for my launching configuration. However, the launch seems to be starting before the sourcemaps finished generating.
|
completed
|
"PreLaunchTask" is not finished before the launching starts I have a simple TypeScript project, and I need to generate sourcemap before debugging.
I have a `tsc` task that does the job, and I set it as the `preLaunchTask` field for my launching configuration. However, the launch seems to be starting before the sourcemaps finished generating.
| 91 |
[] |
0
|
False
|
|
167
|
Windows 10: window not put to foreground in all cases
|
2015-11-19 08:34:28+00:00
|
2015-11-24 15:12:48+00:00
|
Sometimes the VS Code window just flashes in the task bar but is not stored to the foreground (e.g. when running code again from the command line). See https://github.com/atom/electron/issues/2867
|
completed
|
Windows 10: window not put to foreground in all cases Sometimes the VS Code window just flashes in the task bar but is not stored to the foreground (e.g. when running code again from the command line). See https://github.com/atom/electron/issues/2867
| 70 |
[] |
0
|
False
|
|
166
|
Menus wrongly positioned when using multiple monitors
|
2015-11-19 08:33:20+00:00
|
2016-05-06 06:22:34+00:00
|
If you click on the 'File' menu when the main Code window is on the second monitor, the menu appears on the first monitor
https://github.com/atom/atom/issues/3415
|
completed
|
Menus wrongly positioned when using multiple monitors If you click on the 'File' menu when the main Code window is on the second monitor, the menu appears on the first monitor
https://github.com/atom/atom/issues/3415
| 59 |
[] |
0
|
False
|
|
161
|
[php] missing user code auto-complete on 0.10.1
|
2015-11-19 08:09:17+00:00
|
2015-12-03 16:38:28+00:00
|
When writing PHP code VSCode worked well completing user variables beginning with a $ sign or completing user functions. That worked in 0.9.1 but is missing in 0.10.1 - now only PHP built-in code completions are shown.
|
completed
|
[php] missing user code auto-complete on 0.10.1 When writing PHP code VSCode worked well completing user variables beginning with a $ sign or completing user functions. That worked in 0.9.1 but is missing in 0.10.1 - now only PHP built-in code completions are shown.
| 67 |
[] |
0
|
False
|
|
151
|
Support undo and redo in input fields
|
2015-11-19 06:46:57+00:00
|
2017-01-23 15:51:10+00:00
|
How to reproduce the bug:
1. Open a text file;
2. Edit something in the file;
3. Use Cmd+F to activate the search box on the top right;
4. Type a keyword you want to search in the box;
5. Change the keyword in the box; (e.g., add a character to the keyword)
5. Use Cmd+Z to undo;
6. You will notice that Visual Studio Code actually undos the text file edit, not the search keyword edit.
|
completed
|
Support undo and redo in input fields How to reproduce the bug:
1. Open a text file;
2. Edit something in the file;
3. Use Cmd+F to activate the search box on the top right;
4. Type a keyword you want to search in the box;
5. Change the keyword in the box; (e.g., add a character to the keyword)
5. Use Cmd+Z to undo;
6. You will notice that Visual Studio Code actually undos the text file edit, not the search keyword edit.
| 114 |
[] |
0
|
False
|
|
149
|
output window - crashes under load.
|
2015-11-19 06:32:03+00:00
|
2015-11-27 19:40:54+00:00
|
Hi
When configuring the vscode task runner for `"showOutput": "always"`, I note the output window may become overwhelmed if the process emits large amounts of text/data. This results in the application becoming unresponsive and requiring a restart.
Is it possible to buffer any output from a process and page it gracefully to the output window?
Many Thanks
|
completed
|
output window - crashes under load. Hi
When configuring the vscode task runner for `"showOutput": "always"`, I note the output window may become overwhelmed if the process emits large amounts of text/data. This results in the application becoming unresponsive and requiring a restart.
Is it possible to buffer any output from a process and page it gracefully to the output window?
Many Thanks
| 100 |
[] |
0
|
False
|
|
139
|
Crush if dragging a large file to open
|
2015-11-19 03:06:21+00:00
|
2015-11-25 12:54:41+00:00
|
|
completed
|
Crush if dragging a large file to open 
| 62 |
[] |
0
|
False
|
|
138
|
Menus not responsive on Windows 10
|
2015-11-19 03:04:24+00:00
|
2015-11-19 17:55:48+00:00
|
So I created a fresh Windows 10 VM today to try out the Beta. However, the application is sluggish to open which isn't a big deal but I never noticed it before. The problem is that the menus are not working. They will appear on clicking on the menu bar, but selecting a menu item does nothing. If I try to open a project folder from the explorer VSCode opens but the folder does not. I have restarted and reinstalled with a fresh download of the installer. Am I the only one who is seeing this?
|
completed
|
Menus not responsive on Windows 10 So I created a fresh Windows 10 VM today to try out the Beta. However, the application is sluggish to open which isn't a big deal but I never noticed it before. The problem is that the menus are not working. They will appear on clicking on the menu bar, but selecting a menu item does nothing. If I try to open a project folder from the explorer VSCode opens but the folder does not. I have restarted and reinstalled with a fresh download of the installer. Am I the only one who is seeing this?
| 129 |
[] |
0
|
False
|
|
131
|
[less] mixins "{ expected" errors
|
2015-11-19 01:11:50+00:00
|
2016-08-09 20:44:31+00:00
|
When editing a **.less** file unexpected errors show when working with mixins. The error text is `{ expected`. These errors show when using a mixin without wrapping it in a CSS selector or when using a mixin in a media query.
To reproduce take an example from lesscss.org.
http://lesscss.org/features/#loops-feature
http://codepen.io/anon/pen/EjqwNr?editors=010
The Codepen contains code that can be used to replicate `{ expected` errors in Visual Studio Code 0.10.1. In Codepen no errors are shown and the code compiles fine. If this code is put into a **.less** file in Visual Studio Code 0.10.1 you will see the errors on lines 8 and 11. The image below shows the red squiggles signifying the _"errors"_ in the code.
|
completed
|
[less] mixins "{ expected" errors When editing a **.less** file unexpected errors show when working with mixins. The error text is `{ expected`. These errors show when using a mixin without wrapping it in a CSS selector or when using a mixin in a media query.
To reproduce take an example from lesscss.org.
http://lesscss.org/features/#loops-feature
http://codepen.io/anon/pen/EjqwNr?editors=010
The Codepen contains code that can be used to replicate `{ expected` errors in Visual Studio Code 0.10.1. In Codepen no errors are shown and the code compiles fine. If this code is put into a **.less** file in Visual Studio Code 0.10.1 you will see the errors on lines 8 and 11. The image below shows the red squiggles signifying the _"errors"_ in the code.
| 281 |
[] |
0
|
False
|
|
125
|
Goto Symbol doesn't show all functions defined inside the file.
|
2015-11-18 23:54:59+00:00
|
2016-02-10 15:54:24+00:00
|
Using "Go To Symbol..." (⇧⌘O) it seems to only recognize certain ways of declaring functions in javascript.
<img width="607" alt="screen shot 2015-11-18 at 5 49 37 pm" src="https://cloud.githubusercontent.com/assets/1890516/11258194/d1923174-8e1c-11e5-9b2e-a17ba30a97bc.png">
All three functions should show up when you search "searchable", right? Only "searchable" and "alsoSearchable" show up however.
In this case it looks like these cases work:
1. Anonymous function assigned as a property on and object when the object is instantiated.
2. Named function assigned as a property on an object after it's instantiated.
And this case doesn't work:
1. Anonymous function assigned as a property on an object after it's already been instantiated.
This works in Sublime Text and I'd love if it could work in VS Code as well as it's one of the main ways I navigate my javascript code (especially the thousands of lines of code for my game).
|
completed
|
Goto Symbol doesn't show all functions defined inside the file. Using "Go To Symbol..." (⇧⌘O) it seems to only recognize certain ways of declaring functions in javascript.
<img width="607" alt="screen shot 2015-11-18 at 5 49 37 pm" src="https://cloud.githubusercontent.com/assets/1890516/11258194/d1923174-8e1c-11e5-9b2e-a17ba30a97bc.png">
All three functions should show up when you search "searchable", right? Only "searchable" and "alsoSearchable" show up however.
In this case it looks like these cases work:
1. Anonymous function assigned as a property on and object when the object is instantiated.
2. Named function assigned as a property on an object after it's instantiated.
And this case doesn't work:
1. Anonymous function assigned as a property on an object after it's already been instantiated.
This works in Sublime Text and I'd love if it could work in VS Code as well as it's one of the main ways I navigate my javascript code (especially the thousands of lines of code for my game).
| 278 |
[] |
0
|
False
|
|
122
|
Regression: editor text is blurry on Linux with 125% text scaling
|
2015-11-18 23:18:40+00:00
|
2015-12-01 15:53:51+00:00
|
Using Arch Linux with Gnome/Gtk+ 3.18.
In versions 0.9.2 and below, VS Code ignored the text scaling factor in Gnome 3 and rendered its UI text at 100% scale instead of 125% as I had set. (The text scaling factor can be set with gnome-tweak-tool.) To compensate, I set the editor text size to 17, which worked fine.
As of 0.10.1, VS Code now seems to respect the text scaling factor. However, the editor text is noticeably blurry. Changing the editor text size or font does not help. The UI text, on the other hand, seems to be rendered correctly.
I've uploaded comparisons here: http://imgur.com/a/nPLUP
I recommend you view them at 1:1 scale to see the differences clearly.
|
completed
|
Regression: editor text is blurry on Linux with 125% text scaling Using Arch Linux with Gnome/Gtk+ 3.18.
In versions 0.9.2 and below, VS Code ignored the text scaling factor in Gnome 3 and rendered its UI text at 100% scale instead of 125% as I had set. (The text scaling factor can be set with gnome-tweak-tool.) To compensate, I set the editor text size to 17, which worked fine.
As of 0.10.1, VS Code now seems to respect the text scaling factor. However, the editor text is noticeably blurry. Changing the editor text size or font does not help. The UI text, on the other hand, seems to be rendered correctly.
I've uploaded comparisons here: http://imgur.com/a/nPLUP
I recommend you view them at 1:1 scale to see the differences clearly.
| 202 |
[] |
0
|
False
|
|
115
|
Odd code in vscode/src/vs/editor/common/modes/lineStream.ts
|
2015-11-18 22:00:49+00:00
|
2015-11-25 09:42:20+00:00
|
```
private actualStringToArray(str:string):boolean[] {
var maxCharCode = 0;
for (var i = 0; i < str.length; i++) {
maxCharCode = str.charCodeAt(i);
}
var r = [];
for (i = 0; i < maxCharCode; i++) {
r[i] = false;
}
for (i = 0; i < str.length; i++) {
r[str.charCodeAt(i)] = true;
}
return r;
}
```
is the first loop supposed to find the largest Char code? at the moment it will just return the the last character in str.
|
completed
|
Odd code in vscode/src/vs/editor/common/modes/lineStream.ts ```
private actualStringToArray(str:string):boolean[] {
var maxCharCode = 0;
for (var i = 0; i < str.length; i++) {
maxCharCode = str.charCodeAt(i);
}
var r = [];
for (i = 0; i < maxCharCode; i++) {
r[i] = false;
}
for (i = 0; i < str.length; i++) {
r[str.charCodeAt(i)] = true;
}
return r;
}
```
is the first loop supposed to find the largest Char code? at the moment it will just return the the last character in str.
| 177 |
[] |
0
|
False
|
|
106
|
VMW Workstation: VS Code hits 97% CPU and won't start for a couple of minutes
|
2015-11-18 21:18:15+00:00
|
2015-11-26 11:04:42+00:00
|
I'm in VMW Workstation 11.1.3 with a 8GB/single core/Win764bit and when I start code.exe from the start menu, it jumps to 97% of cpu and will take a couple of minutes to start. I'm not opening any folders with code or doing anything with the commandline, this is a plain vanilla start from the menu. I also noticed that I can sometimes speed up the starti[ by starting 4 or 6 instances (each click from the start menu seems to start 2 instances in the taskmanager, but not the desktop) and then the ide will kick in, but I'm left with all the instances until I shut down the ide and then all instances close.
I've seen this same behavior on VMs I've created at work and at home (not the same VM on two different computers).
|
completed
|
VMW Workstation: VS Code hits 97% CPU and won't start for a couple of minutes I'm in VMW Workstation 11.1.3 with a 8GB/single core/Win764bit and when I start code.exe from the start menu, it jumps to 97% of cpu and will take a couple of minutes to start. I'm not opening any folders with code or doing anything with the commandline, this is a plain vanilla start from the menu. I also noticed that I can sometimes speed up the starti[ by starting 4 or 6 instances (each click from the start menu seems to start 2 instances in the taskmanager, but not the desktop) and then the ide will kick in, but I'm left with all the instances until I shut down the ide and then all instances close.
I've seen this same behavior on VMs I've created at work and at home (not the same VM on two different computers).
| 212 |
[] |
0
|
False
|
|
103
|
Tabs don't update column counter
|
2015-11-18 21:08:28+00:00
|
2015-11-23 09:38:53+00:00
|
Repro:
1. Hit the tab key
2. Column count in gutter doesn't update
Forgive the GIF quality.
|
completed
|
Tabs don't update column counter Repro:
1. Hit the tab key
2. Column count in gutter doesn't update
Forgive the GIF quality.
| 93 |
[] |
0
|
False
|
|
102
|
Environment variables are not being defined while debugging
|
2015-11-18 21:03:32+00:00
|
2015-11-19 16:56:29+00:00
|
I use VS Code to start a debugging session and in the configuration I define a value for PORT yet it is always undefined. I cannot seem to access these environment variables. Is there another way to access these environment variables?
`var port = process.env.PORT || 8001;`
Below is the launch.json that I am using for a sample project to try to access environment variables. I'd like to be able to use launch configurations to create multiple configurations with different environment variables.
```
{
"version": "0.1.0",
// List of configurations. Add new configurations or edit existing ones.
"configurations": [
{
// Name of configuration; appears in the launch configuration drop down menu.
"name": "Launch server.js",
// Type of configuration.
"type": "node",
// Workspace relative or absolute path to the program.
"program": "server.js",
// Automatically stop program after launch.
"stopOnEntry": false,
// Command line arguments passed to the program.
"args": [],
// Workspace relative or absolute path to the working directory of the program being debugged. Default is the current workspace.
"cwd": ".",
// Workspace relative or absolute path to the runtime executable to be used. Default is the runtime executable on the PATH.
"runtimeExecutable": null,
// Optional arguments passed to the runtime executable.
"runtimeArgs": ["--nolazy"],
// Environment variables passed to the program.
"env": {
"NODE_ENV": "development",
"PORT" : 8005
},
// Use JavaScript source maps (if they exist).
"sourceMaps": false,
// If JavaScript source maps are enabled, the generated code is expected in this directory.
"outDir": null
},
{
"name": "Attach",
"type": "node",
// TCP/IP address. Default is "localhost".
"address": "localhost",
// Port to attach to.
"port": 5858,
"sourceMaps": false
}
]
}
```
|
completed
|
Environment variables are not being defined while debugging I use VS Code to start a debugging session and in the configuration I define a value for PORT yet it is always undefined. I cannot seem to access these environment variables. Is there another way to access these environment variables?
`var port = process.env.PORT || 8001;`
Below is the launch.json that I am using for a sample project to try to access environment variables. I'd like to be able to use launch configurations to create multiple configurations with different environment variables.
```
{
"version": "0.1.0",
// List of configurations. Add new configurations or edit existing ones.
"configurations": [
{
// Name of configuration; appears in the launch configuration drop down menu.
"name": "Launch server.js",
// Type of configuration.
"type": "node",
// Workspace relative or absolute path to the program.
"program": "server.js",
// Automatically stop program after launch.
"stopOnEntry": false,
// Command line arguments passed to the program.
"args": [],
// Workspace relative or absolute path to the working directory of the program being debugged. Default is the current workspace.
"cwd": ".",
// Workspace relative or absolute path to the runtime executable to be used. Default is the runtime executable on the PATH.
"runtimeExecutable": null,
// Optional arguments passed to the runtime executable.
"runtimeArgs": ["--nolazy"],
// Environment variables passed to the program.
"env": {
"NODE_ENV": "development",
"PORT" : 8005
},
// Use JavaScript source maps (if they exist).
"sourceMaps": false,
// If JavaScript source maps are enabled, the generated code is expected in this directory.
"outDir": null
},
{
"name": "Attach",
"type": "node",
// TCP/IP address. Default is "localhost".
"address": "localhost",
// Port to attach to.
"port": 5858,
"sourceMaps": false
}
]
}
```
| 521 |
[] |
0
|
False
|
|
100
|
GitHub link on page is broken
|
2015-11-18 20:33:35+00:00
|
2015-11-18 20:48:44+00:00
|
https://code.visualstudio.com/Home/Connect points to https://github.com/Microsoft/vscode-distro/ which is a 404
|
completed
|
GitHub link on page is broken https://code.visualstudio.com/Home/Connect points to https://github.com/Microsoft/vscode-distro/ which is a 404
| 46 |
[] |
0
|
False
|
|
94
|
VSCode very slooow when opening minified css file
|
2015-11-18 20:00:01+00:00
|
2015-12-07 10:06:42+00:00
|
Mac OS X El Capitan, 10.11.1,
VSCode 0.10.1
css file size: 116,198 bytes (119 KB on disk)
The attached file was built with a minifier as part of a grunt task to build the distributable files of a website. Tried to open the file several times to make sure that file is the issue. The app eventually shows a dialog that says "Visual Studio is no longer responding"
When I reopen VSCode after the crash, the folder has been forgotten, it opens to a different folder. When is the "current" folder updated to the existing folder?
I added the .txt extension in order to add it here. The file extension was originally just .css
[main.08642f99.css.txt](https://github.com/Microsoft/vscode/files/38262/main.08642f99.css.txt)
|
completed
|
VSCode very slooow when opening minified css file Mac OS X El Capitan, 10.11.1,
VSCode 0.10.1
css file size: 116,198 bytes (119 KB on disk)
The attached file was built with a minifier as part of a grunt task to build the distributable files of a website. Tried to open the file several times to make sure that file is the issue. The app eventually shows a dialog that says "Visual Studio is no longer responding"
When I reopen VSCode after the crash, the folder has been forgotten, it opens to a different folder. When is the "current" folder updated to the existing folder?
I added the .txt extension in order to add it here. The file extension was originally just .css
[main.08642f99.css.txt](https://github.com/Microsoft/vscode/files/38262/main.08642f99.css.txt)
| 213 |
[] |
0
|
False
|
|
86
|
PHP autocompletion: $_GET completes into $$_GET
|
2015-11-18 18:54:48+00:00
|
2015-11-22 15:39:13+00:00
|
When using autocompletion for variables it places 2 dollar signs instead of 1. For example typing $_GET will transform it into $$_GET. Fails with every completion starting with $.
|
completed
|
PHP autocompletion: $_GET completes into $$_GET When using autocompletion for variables it places 2 dollar signs instead of 1. For example typing $_GET will transform it into $$_GET. Fails with every completion starting with $.
| 63 |
[] |
0
|
False
|
|
80
|
Windows setup file version
|
2015-11-18 18:19:10+00:00
|
2015-11-26 09:54:24+00:00
|
windows setup not have a file version and when hover cursor 0.0.0.0 shown. please set setup file version
|
completed
|
Windows setup file version windows setup not have a file version and when hover cursor 0.0.0.0 shown. please set setup file version
| 30 |
[] |
0
|
False
|
|
79
|
Getting "Visual Studio Code has crashed" a few times
|
2015-11-18 18:15:29+00:00
|
2015-11-26 19:15:23+00:00
|
The last three days, when I come into work, I get this dialog. Is there an error log or crash dump I can attach that will help to diagnose?
|
completed
|
Getting "Visual Studio Code has crashed" a few times The last three days, when I come into work, I get this dialog. Is there an error log or crash dump I can attach that will help to diagnose?
| 51 |
[] |
0
|
False
|
|
69
|
Proxy support for extension gallery
|
2015-11-18 17:22:44+00:00
|
2016-01-04 16:41:42+00:00
|
Whenever I try to install any extension, using _ext install_, I get a **connect ETIMEDOUT 191.238.172.191:443** error.
Trying to navigate to **https://191.238.172.191** in the browser produces a warning regarding the certificate being valid only for ***.market.visualstudio.com**, but I'm allowed to proceed.
Shouldn't VSCode try to connect to the name instead of the IP?
I'm behind a proxy, VSCode updates just fine behind it, and also lists the available extensions. The firewall here logs the invalid certificate but allows the connection to proceed. Doesn't look like a problem in my end...
**OS:** Windows 7
**VSCode:** 0.10.1
|
completed
|
Proxy support for extension gallery Whenever I try to install any extension, using _ext install_, I get a **connect ETIMEDOUT 191.238.172.191:443** error.
Trying to navigate to **https://191.238.172.191** in the browser produces a warning regarding the certificate being valid only for ***.market.visualstudio.com**, but I'm allowed to proceed.
Shouldn't VSCode try to connect to the name instead of the IP?
I'm behind a proxy, VSCode updates just fine behind it, and also lists the available extensions. The firewall here logs the invalid certificate but allows the connection to proceed. Doesn't look like a problem in my end...
**OS:** Windows 7
**VSCode:** 0.10.1
| 180 |
[] |
0
|
False
|
|
66
|
Git conflict highlighting can get messed up easily
|
2015-11-18 17:16:01+00:00
|
2016-02-22 17:17:33+00:00
|
Ubuntu 12.04, vscode 0.10.1
Deleting and undoing the line doubles the highlight: (stays after closing and reopening the file)
Deleting from the end of the line above the `=======` to the end of the line starting with `>>>>>>>`:
Undoing the above results in this:
|
completed
|
Git conflict highlighting can get messed up easily Ubuntu 12.04, vscode 0.10.1
Deleting and undoing the line doubles the highlight: (stays after closing and reopening the file)
Deleting from the end of the line above the `=======` to the end of the line starting with `>>>>>>>`:
Undoing the above results in this:
| 239 |
[] |
0
|
False
|
|
64
|
Rounded selection seems broken due to current word highlight
|
2015-11-18 17:11:43+00:00
|
2015-12-09 15:24:22+00:00
|
editor.roundedSelection is broken
- If our selection doesn't span multiple lines, the selection is still squared.
|
completed
|
Rounded selection seems broken due to current word highlight editor.roundedSelection is broken
- If our selection doesn't span multiple lines, the selection is still squared.
| 155 |
[] |
0
|
False
|
|
55
|
Searching large projects is too slow
|
2015-11-18 16:28:12+00:00
|
2018-04-30 04:54:40+00:00
|
Ubuntu 12.04, vscode 0.10.1
I have found Go to file's indexing against a full Chromium workspace to be very slow. It took ~40 seconds to find "Tab.java" whereas a simple `find` command took less than a second:
```
$ time find . -name "Tab.java"
./chrome/android/java/src/org/chromium/chrome/browser/tab/Tab.java
real 0m0.559s
user 0m0.268s
sys 0m0.284s
```
Note that the workspace is on an SSD.
|
completed
|
Searching large projects is too slow Ubuntu 12.04, vscode 0.10.1
I have found Go to file's indexing against a full Chromium workspace to be very slow. It took ~40 seconds to find "Tab.java" whereas a simple `find` command took less than a second:
```
$ time find . -name "Tab.java"
./chrome/android/java/src/org/chromium/chrome/browser/tab/Tab.java
real 0m0.559s
user 0m0.268s
sys 0m0.284s
```
Note that the workspace is on an SSD.
| 143 |
[] |
0
|
False
|
|
51
|
Fix add selection above and add selection below hotkey on Ubuntu
|
2015-11-18 16:18:25+00:00
|
2015-11-27 11:09:47+00:00
|
I'm used to `alt+shift+up` and `alt+shift+down` expanding the selection above and below the current anchor, as far as I can see this is not implemented in core or an extension.
Edit: This is actually implemented and working fine, the hotkey ctrl+alt+up/down just conflicts with the Ubuntu OS hotkey to change workspace.
|
completed
|
Fix add selection above and add selection below hotkey on Ubuntu I'm used to `alt+shift+up` and `alt+shift+down` expanding the selection above and below the current anchor, as far as I can see this is not implemented in core or an extension.
Edit: This is actually implemented and working fine, the hotkey ctrl+alt+up/down just conflicts with the Ubuntu OS hotkey to change workspace.
| 102 |
[] |
0
|
False
|
|
42
|
Document symbols are duplicated
|
2015-11-18 14:30:13+00:00
|
2015-11-26 14:41:54+00:00
|
When adding a 2nd document symbol provider, let's say for typescript, all entries are duplicated. When adding a 3rd, they are triplicated, etc...
|
completed
|
Document symbols are duplicated When adding a 2nd document symbol provider, let's say for typescript, all entries are duplicated. When adding a 3rd, they are triplicated, etc...
| 47 |
[] |
0
|
False
|
|
39
|
broken selection feedback when selecting bold text in markdown files
|
2015-11-17 22:09:59+00:00
|
2015-11-19 08:27:45+00:00
|
- open a markdown file with bold markup, e.g.
abc **text** xyz
- try to select the line with the mouse starting at 'abc' and slowly extending to 'xyz'
Observe: if you reach the second '**', the selection of '**text**' disappears. In the end you have two disconnected selection ranges.
- in addition I see lots of flashing selection changes while dragging the mouse
|
completed
|
broken selection feedback when selecting bold text in markdown files - open a markdown file with bold markup, e.g.
abc **text** xyz
- try to select the line with the mouse starting at 'abc' and slowly extending to 'xyz'
Observe: if you reach the second '**', the selection of '**text**' disappears. In the end you have two disconnected selection ranges.
- in addition I see lots of flashing selection changes while dragging the mouse
| 115 |
[] |
0
|
False
|
|
37
|
vscode "--extensionHomePath" option does not work when used with the vscode proxy
|
2015-11-17 14:50:06+00:00
|
2015-11-19 12:45:33+00:00
|
I'm developing an extension and want to test its installation from the gallery. After installing it from the gallery, I want to continue development in the VSCode extension host. When launching the extension through F5, I see the annoying extension override warning in the extension host window.
To prevent that the ~/.vscode/extensions path is used in that case, I tried to use the " --extensionHomePath" in the extensionHost launch config and specify an empty directory.
But it seems that the "--extensionHomePath" isn't honoured in this case (probably because vscode is a proxy that connects to an already running vscode).
BTW, it would be cool if "--extensionHomePath" would allow an empty path.
|
completed
|
vscode "--extensionHomePath" option does not work when used with the vscode proxy I'm developing an extension and want to test its installation from the gallery. After installing it from the gallery, I want to continue development in the VSCode extension host. When launching the extension through F5, I see the annoying extension override warning in the extension host window.
To prevent that the ~/.vscode/extensions path is used in that case, I tried to use the " --extensionHomePath" in the extensionHost launch config and specify an empty directory.
But it seems that the "--extensionHomePath" isn't honoured in this case (probably because vscode is a proxy that connects to an already running vscode).
BTW, it would be cool if "--extensionHomePath" would allow an empty path.
| 204 |
[] |
0
|
False
|
|
36
|
[Git] weird indicator for renamed file
|
2015-11-17 14:00:18+00:00
|
2016-05-31 08:03:05+00:00
|
(I am on Mac OS X, Git 2.4.0)
- have a checked in README.md with some contents
- take the contents of the file and move it to a new file CONTRIBUTING.md
- change the text in README.md to something else
- stage all
|
completed
|
[Git] weird indicator for renamed file (I am on Mac OS X, Git 2.4.0)
- have a checked in README.md with some contents
- take the contents of the file and move it to a new file CONTRIBUTING.md
- change the text in README.md to something else
- stage all
| 128 |
[] |
0
|
False
|
|
34
|
Javascript - regular expressions are not colored - Javascript mode instantiated twice
|
2015-11-17 10:36:00+00:00
|
2015-11-19 08:36:07+00:00
|
New **javascript** file, use the following code snippet:
`var booleanRegex = /^true|false$/i;`
`var stringRegex = /^(['"]).*\1$/;`
Notice the regex value **does not get colored**.
Regex coloring works for Typescript.
|
completed
|
Javascript - regular expressions are not colored - Javascript mode instantiated twice New **javascript** file, use the following code snippet:
`var booleanRegex = /^true|false$/i;`
`var stringRegex = /^(['"]).*\1$/;`
Notice the regex value **does not get colored**.
Regex coloring works for Typescript.
| 99 |
[] |
0
|
False
|
|
33
|
build errors: vscode.d.ts is not found
|
2015-11-16 21:00:33+00:00
|
2015-11-17 09:11:42+00:00
|
when running build I am seeing +400 errors, all of them related to vscode.d.ts.
```
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(434,19): Cannot find namespace 'vscode'.
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(437,24): Cannot find namespace 'vscode'.
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(437,46): Cannot find namespace 'vscode'.
....
*** Error: vscode/extensions/declares.d.ts(59,51): Cannot find name 'Thenable'.
*** Error: vscode/extensions/vscode-api-tests/src/window.test.ts(9,33): Cannot find module 'vscode'.
*** Finished with 408 errors.
```
...
|
completed
|
build errors: vscode.d.ts is not found when running build I am seeing +400 errors, all of them related to vscode.d.ts.
```
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(434,19): Cannot find namespace 'vscode'.
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(437,24): Cannot find namespace 'vscode'.
*** Error: vscode/src/vs/workbench/api/common/pluginHostTypes.ts(437,46): Cannot find namespace 'vscode'.
....
*** Error: vscode/extensions/declares.d.ts(59,51): Cannot find name 'Thenable'.
*** Error: vscode/extensions/vscode-api-tests/src/window.test.ts(9,33): Cannot find module 'vscode'.
*** Finished with 408 errors.
```
...
| 258 |
[] |
0
|
False
|
|
32
|
Program appears to continue executing after pressing stop in the debugger
|
2015-11-16 15:11:38+00:00
|
2015-11-22 22:50:59+00:00
|
In a simple node app, I step through a loop in the debugger. Before exiting the loop, I press the stop button
I expect the program to stop executing right at that point but it appears to continue executing due to the fact that the console.log statement is executed (highlighted below) and the value of the string being output looks like the loop continued to execute even after pressing stop:
|
completed
|
Program appears to continue executing after pressing stop in the debugger In a simple node app, I step through a loop in the debugger. Before exiting the loop, I press the stop button
I expect the program to stop executing right at that point but it appears to continue executing due to the fact that the console.log statement is executed (highlighted below) and the value of the string being output looks like the loop continued to execute even after pressing stop:
| 224 |
[] |
0
|
False
|
|
31
|
Extension uninstall leaves empty directories behind
|
2015-11-16 14:32:17+00:00
|
2016-07-05 14:07:36+00:00
|
I install eslint and jshint and uninstalled them again. I still had two directories in ~/.vscode/extensions for dbaeumer.jshint and dbaeumer.eslint with no package.json. On the next start of VSCode it complained about missing package.json files. I needed to delete the folders manually
|
completed
|
Extension uninstall leaves empty directories behind I install eslint and jshint and uninstalled them again. I still had two directories in ~/.vscode/extensions for dbaeumer.jshint and dbaeumer.eslint with no package.json. On the next start of VSCode it complained about missing package.json files. I needed to delete the folders manually
| 94 |
[] |
0
|
False
|
|
30
|
Variables in local window stop stop updating their value when stepping through code quickly
|
2015-11-16 13:09:43+00:00
|
2015-11-23 14:59:17+00:00
|
In a node express app I have the following loop:
var msg = 'hello world';
var i = 0;
while (i < 100) {
msg = msg + i.toString();
i++;
}
I set up the local and watch windows in the debugger so that I can see the msg variable in both.
When stepping through the loop, if I press F10 very quickly, eventually the msg variable in the locals window will stop updating. See the screenshot below
When stepping through quickly, I sometimes see a message in the watch window that says 'Exception while processing request'
This is on 0.10.0
|
completed
|
Variables in local window stop stop updating their value when stepping through code quickly In a node express app I have the following loop:
var msg = 'hello world';
var i = 0;
while (i < 100) {
msg = msg + i.toString();
i++;
}
I set up the local and watch windows in the debugger so that I can see the msg variable in both.
When stepping through the loop, if I press F10 very quickly, eventually the msg variable in the locals window will stop updating. See the screenshot below
When stepping through quickly, I sometimes see a message in the watch window that says 'Exception while processing request'
This is on 0.10.0
| 217 |
[] |
0
|
False
|
|
28
|
No blue icon on linux
|
2015-11-16 10:30:14+00:00
|
2015-11-16 11:07:24+00:00
|
I see the blue icon with 0.9 builds, but not with 0.10.1 builds.
Only a generic tool icon is shown.
|
completed
|
No blue icon on linux I see the blue icon with 0.9 builds, but not with 0.10.1 builds.
Only a generic tool icon is shown.
| 36 |
[] |
0
|
False
|
|
27
|
Bundled files don't have a top copyright statement
|
2015-11-16 10:06:02+00:00
|
2015-11-16 10:22:56+00:00
|
Latest Build, open workbench.main.js.
Observe: the file doesn't have a top copyright statement. It starts with some code. Also observe that at the end of the file there are a lot of MS copyright statements. Seems that bundling doesn't treat them well.
|
completed
|
Bundled files don't have a top copyright statement Latest Build, open workbench.main.js.
Observe: the file doesn't have a top copyright statement. It starts with some code. Also observe that at the end of the file there are a lot of MS copyright statements. Seems that bundling doesn't treat them well.
| 79 |
[] |
0
|
False
|
|
23
|
[xml] Element and attribute in light and dark theme use same colors
|
2015-11-16 09:35:52+00:00
|
2015-11-27 15:48:38+00:00
|
|
completed
|
[xml] Element and attribute in light and dark theme use same colors 
| 70 |
[] |
0
|
False
|
|
21
|
[vb] Block comment is not colored
|
2015-11-16 09:26:01+00:00
|
2015-12-09 10:07:00+00:00
|
While line comments are nicely colored, block comments are not.
|
completed
|
[vb] Block comment is not colored While line comments are nicely colored, block comments are not.
| 27 |
[] |
0
|
False
|
|
19
|
PHP: extension console.logs when completing function
|
2015-11-16 08:49:55+00:00
|
2015-11-24 16:41:40+00:00
|
Complete a function and find something in the log:
[Plugin Host] provideSignatureHelp
workbench.main.js:1675 [Plugin Host] Object {signatures: Array[1], activeSignature: 0, activeParameter: 0}
|
completed
|
PHP: extension console.logs when completing function Complete a function and find something in the log:
[Plugin Host] provideSignatureHelp
workbench.main.js:1675 [Plugin Host] Object {signatures: Array[1], activeSignature: 0, activeParameter: 0}
| 73 |
[] |
0
|
False
|
|
18
|
Python: Block comment is three single quotes and not two
|
2015-11-16 08:45:27+00:00
|
2015-11-16 11:29:30+00:00
|
When using the block comment feature, only 2 single quotes are put in, instead of three.
|
completed
|
Python: Block comment is three single quotes and not two When using the block comment feature, only 2 single quotes are put in, instead of three.
| 35 |
[] |
0
|
False
|
|
16
|
[f#] Block comment not colored as comment
|
2015-11-16 07:45:57+00:00
|
2017-02-22 22:00:01+00:00
|
Using the block comment in F# adds the following around 'samplesLabel':
``` F#
let mutable (*samplesLabel*) : System.Windows.Forms.Label = null
```
This is however not colored as a comment in VS Code.
|
completed
|
[f#] Block comment not colored as comment Using the block comment in F# adds the following around 'samplesLabel':
``` F#
let mutable (*samplesLabel*) : System.Windows.Forms.Label = null
```
This is however not colored as a comment in VS Code.
| 74 |
[] |
0
|
False
|
|
14
|
C#: Line/Block comment does not work
|
2015-11-16 07:22:24+00:00
|
2015-11-16 08:45:11+00:00
|
I cannot set a line or block comment in C# files anymore.
|
completed
|
C#: Line/Block comment does not work I cannot set a line or block comment in C# files anymore.
| 27 |
[] |
0
|
False
|
|
12
|
[clojure] Block comment is not colored any different
|
2015-11-16 07:02:43+00:00
|
2015-12-09 10:10:21+00:00
|
Have a clojure file and toggle a block comment somewhere. The code after the block comment is not colored as a comment at all.
|
completed
|
[clojure] Block comment is not colored any different Have a clojure file and toggle a block comment somewhere. The code after the block comment is not colored as a comment at all.
| 46 |
[] |
0
|
False
|
|
10
|
Cannot find module 'sinon' when running test/run.sh from terminal
|
2015-11-15 18:54:49+00:00
|
2015-11-16 12:58:13+00:00
|
open terminal
cd vscode/tests
./run.sh
result:
Detail: { [Error: Cannot find module 'sinon'] code: 'MODULE_NOT_FOUND' }
|
completed
|
Cannot find module 'sinon' when running test/run.sh from terminal open terminal
cd vscode/tests
./run.sh
result:
Detail: { [Error: Cannot find module 'sinon'] code: 'MODULE_NOT_FOUND' }
| 66 |
[] |
0
|
False
|
|
9
|
Extension development: null and undefined values not printed to debug repl
|
2015-11-15 12:05:39+00:00
|
2015-11-19 08:11:29+00:00
|
When using console.log() with null or undefined values from an extension, no output shows up in the debug repl making it very hard to understand what is going on at that time.
|
completed
|
Extension development: null and undefined values not printed to debug repl When using console.log() with null or undefined values from an extension, no output shows up in the debug repl making it very hard to understand what is going on at that time.
| 62 |
[] |
0
|
False
|
|
8
|
Flash between opening of workspaces, reload
|
2015-11-14 12:53:12+00:00
|
2015-11-19 10:26:08+00:00
|
start code
set a dark theme _other than the default dark theme_ if you don't already run with a dark theme
file | open folder -> pick any folder
file | open folder -> pick some other folder
result: you'll see a delay/flash between opening of workspaces.
|
completed
|
Flash between opening of workspaces, reload start code
set a dark theme _other than the default dark theme_ if you don't already run with a dark theme
file | open folder -> pick any folder
file | open folder -> pick some other folder
result: you'll see a delay/flash between opening of workspaces.
| 76 |
[] |
0
|
False
|
|
6
|
Windows only - OmniSharp does not provide IntelliSense for strong named assemblies
|
2015-11-13 16:50:44+00:00
|
2016-01-20 09:30:16+00:00
|
upgrade to rc1 dnx/runtime
``` bash
git clone https://github.com/natemcmaster/test-vscode-strong-name
cd test-vscode-strong-name
dnu restore
code .
```
pick the Test project.json
result => "Internal Class InternalClass is not accessible..." error.
Works on OSX
|
completed
|
Windows only - OmniSharp does not provide IntelliSense for strong named assemblies upgrade to rc1 dnx/runtime
``` bash
git clone https://github.com/natemcmaster/test-vscode-strong-name
cd test-vscode-strong-name
dnu restore
code .
```
pick the Test project.json
result => "Internal Class InternalClass is not accessible..." error.
Works on OSX
| 109 |
[] |
0
|
False
|
|
5
|
welcome.md packaged wrongly
|
2015-11-13 16:48:18+00:00
|
2015-11-14 05:42:28+00:00
|
VSCode > Help > Show Welcome > does not work
If I look at the contents of my VSCode package I see a top level resource folder containing a welcome.md. This looks badly placed
|
completed
|
welcome.md packaged wrongly VSCode > Help > Show Welcome > does not work
If I look at the contents of my VSCode package I see a top level resource folder containing a welcome.md. This looks badly placed
| 52 |
[] |
0
|
False
|
|
4
|
C# bracket insertion, indentation not working
|
2015-11-13 16:45:06+00:00
|
2015-11-16 11:29:58+00:00
|
Type if (
expected => closing )
actual => nothing
|
completed
|
C# bracket insertion, indentation not working Type if (
expected => closing )
actual => nothing
| 25 |
[] |
0
|
False
|
|
3
|
Omnisharp not included in Linux build
|
2015-11-13 16:34:23+00:00
|
2015-11-14 06:32:48+00:00
|
Our linux build machine does not include the csharp-o/**bin** folder.
1. Running `scripts/npm.sh install` -> csharp-o/**bin** folder nicely gets created on my linux machine.
2. Running `gulp vscode-linux-x64` also nicely creates the csharp-o/**bin** folder on my linux machine.
Something is strange on our build machine
|
completed
|
Omnisharp not included in Linux build Our linux build machine does not include the csharp-o/**bin** folder.
1. Running `scripts/npm.sh install` -> csharp-o/**bin** folder nicely gets created on my linux machine.
2. Running `gulp vscode-linux-x64` also nicely creates the csharp-o/**bin** folder on my linux machine.
Something is strange on our build machine
| 109 |
[] |
0
|
False
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.