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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
1257
|
'There is a task running' warning after developping a extension
|
2015-12-14 13:00:56+00:00
|
2015-12-15 14:08:05+00:00
|
- open a folder that contains code of an extension
- debug the extension
- close the extension window (debugger connection correctly gets closed)
- in the window switch to a different folder
Warning appears
'There is a task running. Do you want to terminate it'
It is not clear to me what task that is. At the very least it could show the name of the task.
|
completed
|
'There is a task running' warning after developping a extension - open a folder that contains code of an extension
- debug the extension
- close the extension window (debugger connection correctly gets closed)
- in the window switch to a different folder
Warning appears
'There is a task running. Do you want to terminate it'
It is not clear to me what task that is. At the very least it could show the name of the task.
| 99 |
[] |
0
|
False
|
|
1256
|
I am not seeing extension error/warnings indication in status bar
|
2015-12-14 12:57:55+00:00
|
2015-12-14 15:37:12+00:00
|
I tried the following scenarios on mac:
- causing an error in an extension by making its package.json invalid
- installing the same extension twice with different name so that one overrides the other
I get errors and warnings for both in the dev console, so I assume that the status bar indicator does just not work for me.
|
completed
|
I am not seeing extension error/warnings indication in status bar I tried the following scenarios on mac:
- causing an error in an extension by making its package.json invalid
- installing the same extension twice with different name so that one overrides the other
I get errors and warnings for both in the dev console, so I assume that the status bar indicator does just not work for me.
| 140 |
[] |
0
|
False
|
|
1254
|
Long text wraps in debug console cuts CJK strings
|
2015-12-14 12:02:15+00:00
|
2016-01-06 10:55:37+00:00
|
Test file:
``` javascript
var str1 = "三代之時，天下有國千萬，言語不通。周既王，始有雅言。諸子著作，皆以雅言。及周道微，天下紛亂，言語異聲，文字異形。尤是楚語至不同也。秦始皇帝混一車書，獨用秦篆，各地方言日合。然至於許慎之世，說文解字之所錄，亦有同義而音異之字，多有「某地曰某為某」之訓。蓋天下文字雖一，而言語未統也。此上古音也。古語於語法異於今音，可見諸尚書。"
var str2 = "Chinese (汉语 / 漢語; Hànyǔ or 中文; Zhōngwén) is a group of related but in many cases mutually unintelligible language varieties, forming a branch of the Sino-Tibetan language family. Chinese is spoken by the Han majority and many other ethnic groups in China. Nearly 1.2 billion people (around 16% of the world's population) speak some form of Chinese as their first language."
console.log(str1);
console.log(str2);
console.log('DONE');
```
Cheap solution (done in terminals for example):
- measure also a typical wide character width. e.g. : https://github.com/Microsoft/vscode/blob/master/src/vs/editor/browser/config/configuration.ts#L70
- when computing the width of the string use the wide character width where applicable. e.g. : https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/viewModel/characterHardWrappingLineMapper.ts#L174
- this will of course not help with all languages (like arabic, thai), but would be a first improvement.
|
completed
|
Long text wraps in debug console cuts CJK strings 
Test file:
``` javascript
var str1 = "三代之時，天下有國千萬，言語不通。周既王，始有雅言。諸子著作，皆以雅言。及周道微，天下紛亂，言語異聲，文字異形。尤是楚語至不同也。秦始皇帝混一車書，獨用秦篆，各地方言日合。然至於許慎之世，說文解字之所錄，亦有同義而音異之字，多有「某地曰某為某」之訓。蓋天下文字雖一，而言語未統也。此上古音也。古語於語法異於今音，可見諸尚書。"
var str2 = "Chinese (汉语 / 漢語; Hànyǔ or 中文; Zhōngwén) is a group of related but in many cases mutually unintelligible language varieties, forming a branch of the Sino-Tibetan language family. Chinese is spoken by the Han majority and many other ethnic groups in China. Nearly 1.2 billion people (around 16% of the world's population) speak some form of Chinese as their first language."
console.log(str1);
console.log(str2);
console.log('DONE');
```
Cheap solution (done in terminals for example):
- measure also a typical wide character width. e.g. : https://github.com/Microsoft/vscode/blob/master/src/vs/editor/browser/config/configuration.ts#L70
- when computing the width of the string use the wide character width where applicable. e.g. : https://github.com/Microsoft/vscode/blob/master/src/vs/editor/common/viewModel/characterHardWrappingLineMapper.ts#L174
- this will of course not help with all languages (like arabic, thai), but would be a first improvement.
| 513 |
[] |
0
|
False
|
|
1251
|
html file interfers with js file
|
2015-12-14 11:45:00+00:00
|
2015-12-14 13:57:33+00:00
|
- two files
``` javascript
class A {
}
let x = 10;
const z = 10;
```
``` html
<script type="text/javascript">
var i = 10;
if (i < 5) {
// some code
}
class A {
}
let x = 10;
const z = 5;
z = 10;
</script>
```
JavaScript file shows errors about double symbols. Is this expected.
|
completed
|
html file interfers with js file - two files
``` javascript
class A {
}
let x = 10;
const z = 10;
```
``` html
<script type="text/javascript">
var i = 10;
if (i < 5) {
// some code
}
class A {
}
let x = 10;
const z = 5;
z = 10;
</script>
```
JavaScript file shows errors about double symbols. Is this expected.
| 102 |
[] |
0
|
False
|
|
1249
|
Breakpoints not vertically centered wity line number
|
2015-12-14 10:58:01+00:00
|
2016-02-02 13:42:38+00:00
|
Linux
Version 0.10.4
Commit 18c4a65cb26517c25ce0f487feb6d169145bc647
The breakpoints could be nicer aligned with the line numbers
|
completed
|
Breakpoints not vertically centered wity line number Linux
Version 0.10.4
Commit 18c4a65cb26517c25ce0f487feb6d169145bc647
The breakpoints could be nicer aligned with the line numbers
| 109 |
[] |
0
|
False
|
|
1248
|
window.showErrorMessage: returned item is undefined if close is selected
|
2015-12-14 10:55:00+00:00
|
2015-12-18 09:56:14+00:00
|
- use window.showErrorMessage with a custom message.
- when the message appears press the close button
Observe: the resolved value for the item is undefined. IMO it should be an item representing the close button
|
completed
|
window.showErrorMessage: returned item is undefined if close is selected - use window.showErrorMessage with a custom message.
- when the message appears press the close button
Observe: the resolved value for the item is undefined. IMO it should be an item representing the close button
| 73 |
[] |
0
|
False
|
|
1247
|
Cannot close without saving
|
2015-12-14 10:48:33+00:00
|
2015-12-14 15:16:34+00:00
|
- open vscode
- ctrl+shift+n to get a new instance
- type in the untitled file
- close
- click do not save
- it doesn't close
|
completed
|
Cannot close without saving - open vscode
- ctrl+shift+n to get a new instance
- type in the untitled file
- close
- click do not save
- it doesn't close
| 100 |
[] |
0
|
False
|
|
1246
|
[json] Intellisense missing for jsconfig.json
|
2015-12-14 10:32:31+00:00
|
2015-12-14 11:59:38+00:00
|
@aeschli
|
completed
|
[json] Intellisense missing for jsconfig.json 
@aeschli
| 70 |
[] |
0
|
False
|
|
1243
|
"Zoom Out" does not work as expected if window.zoomLevel > 0
|
2015-12-14 10:28:12+00:00
|
2015-12-14 17:10:05+00:00
|
- set window.zoomLevel to 5.
- try to zoom out.
Observe: Multiple "Zoom out" do not bring the zoom level to an non-zoomed state.
|
completed
|
"Zoom Out" does not work as expected if window.zoomLevel > 0 - set window.zoomLevel to 5.
- try to zoom out.
Observe: Multiple "Zoom out" do not bring the zoom level to an non-zoomed state.
| 63 |
[] |
0
|
False
|
|
1239
|
files.trimTrailingWhitespace not working
|
2015-12-14 09:58:47+00:00
|
2015-12-14 15:33:39+00:00
|
When i enable this option like so (User Settings):
```
"files.trimTrailingWhitespace": true
```
then it does not delete whitespaces on save.
Here are my user settings:
```
{
"editor.renderWhitespace": true,
"files.trimTrailingWhitespace": true
}
```
OS: Windows 10 Pro
|
completed
|
files.trimTrailingWhitespace not working When i enable this option like so (User Settings):
```
"files.trimTrailingWhitespace": true
```
then it does not delete whitespaces on save.
Here are my user settings:
```
{
"editor.renderWhitespace": true,
"files.trimTrailingWhitespace": true
}
```
OS: Windows 10 Pro
| 97 |
[] |
0
|
False
|
|
1238
|
Markdown Header Incorrect Syntax Highlighting
|
2015-12-14 09:44:19+00:00
|
2016-06-16 16:19:47+00:00
|
When there is a valid `#` in the header, the syntax highlighter for markdown misunderstands it to be the termination of the header.
<img width="963" alt="test_md_-_workshop-materials-1-8" src="https://cloud.githubusercontent.com/assets/1282577/11777576/31e73a04-a247-11e5-8a02-0a1c91e4c8ae.png">
I would be glad to help, but would need to get pointed in the right direction in the code to understand where I can make the change and submit a PR.
|
completed
|
Markdown Header Incorrect Syntax Highlighting When there is a valid `#` in the header, the syntax highlighter for markdown misunderstands it to be the termination of the header.
<img width="963" alt="test_md_-_workshop-materials-1-8" src="https://cloud.githubusercontent.com/assets/1282577/11777576/31e73a04-a247-11e5-8a02-0a1c91e4c8ae.png">
I would be glad to help, but would need to get pointed in the right direction in the code to understand where I can make the change and submit a PR.
| 160 |
[] |
0
|
False
|
|
1236
|
Incorrect visualising markdown table
|
2015-12-14 03:23:11+00:00
|
2016-06-16 16:20:30+00:00
|
When I want to indent the table, the markdown visualisation fail. The same format works perfectly on GitHub.
|
completed
|
Incorrect visualising markdown table When I want to indent the table, the markdown visualisation fail. The same format works perfectly on GitHub.
| 159 |
[] |
0
|
False
|
|
1234
|
New files not getting jsconfig
|
2015-12-14 02:54:59+00:00
|
2015-12-14 15:43:22+00:00
|
When I create a new file, it does not recognize the jsconfig settings (ES6 for example). I need to go to jsconfig, make a change, dismake that change and then it the new file will be ok.
|
completed
|
New files not getting jsconfig When I create a new file, it does not recognize the jsconfig settings (ES6 for example). I need to go to jsconfig, make a change, dismake that change and then it the new file will be ok.
| 60 |
[] |
0
|
False
|
|
1229
|
errors generated by a task with isWatching not cleared after fixing
|
2015-12-13 16:46:58+00:00
|
2015-12-14 08:56:29+00:00
|
See http://stackoverflow.com/questions/33563049/in-vscode-errors-generated-by-a-task-with-iswatching-are-not-always-cleared-afte
The question and answer are both correct in their description. I'm having the same problem and couldn't find a corresponding issue here in the repo, so figured I'd go ahead and create one.
|
completed
|
errors generated by a task with isWatching not cleared after fixing See http://stackoverflow.com/questions/33563049/in-vscode-errors-generated-by-a-task-with-iswatching-are-not-always-cleared-afte
The question and answer are both correct in their description. I'm having the same problem and couldn't find a corresponding issue here in the repo, so figured I'd go ahead and create one.
| 116 |
[] |
0
|
False
|
|
1226
|
Disappeared refereneces hint with specific sdk version
|
2015-12-13 08:19:22+00:00
|
2015-12-14 14:55:38+00:00
|
I changed omnisharp sdk version from 1.0.0-beta4 to 1.0.0-rc1-update1 via this command:
```
vim /Applications/Visual\ Studio\ Code.app/Contents/Resources/app/extensions/csharp-o/bin/gl
obal.json
```
and then open the vscode, the status bar display the omnisharp is running, but the references hint is disappeared, in addition I can't go to definition.
but when I set the the sdk version in global.json under solution folder as follow, the references hint and the function 'go to definition' works fine:
```
{
"projects": [
"Src",
"Test"
],
"sdk": {
"version": "1.0.0-rc1-update1"
}
}
```
my mac OS X version is 10.11.1, the output of dnvm list looks like:
```
Active Version Runtime Architecture OperatingSystem Alias
------ ------- ------- ------------ --------------- -----
* 1.0.0-rc1-final coreclr x64 darwin default
1.0.0-rc1-update1 mono linux/osx
```
|
completed
|
Disappeared refereneces hint with specific sdk version I changed omnisharp sdk version from 1.0.0-beta4 to 1.0.0-rc1-update1 via this command:
```
vim /Applications/Visual\ Studio\ Code.app/Contents/Resources/app/extensions/csharp-o/bin/gl
obal.json
```
and then open the vscode, the status bar display the omnisharp is running, but the references hint is disappeared, in addition I can't go to definition.
but when I set the the sdk version in global.json under solution folder as follow, the references hint and the function 'go to definition' works fine:
```
{
"projects": [
"Src",
"Test"
],
"sdk": {
"version": "1.0.0-rc1-update1"
}
}
```
my mac OS X version is 10.11.1, the output of dnvm list looks like:
```
Active Version Runtime Architecture OperatingSystem Alias
------ ------- ------- ------------ --------------- -----
* 1.0.0-rc1-final coreclr x64 darwin default
1.0.0-rc1-update1 mono linux/osx
```
| 281 |
[] |
0
|
False
|
|
1224
|
[css] Browsers without version number don’t show in CSS IntelliSense
|
2015-12-12 22:45:14+00:00
|
2016-01-12 11:38:00+00:00
|
The css-scheme.xml file often includes a browser token without a version number, to either mean all versions, or perhaps that the version number is unknown. This is common for Chrome as it came into existence after many versions of Safari, and I followed that pattern for Edge (using E, rather than E12).
These browser do not show up in the CSS IntelliSense.
Steps to repo:
Start typing :corner-present
Expected:
(Chrome, Safari 5)
Actual:
(Safari 5).
I could fix this for Edge by changing all E's to E12, but for Chrome it would be a lot of research to see if only "C" is listed because it is since Chrome 1 or if it is because the version is unknown. BrowserStack only goes back to Chrome14.
|
completed
|
[css] Browsers without version number don’t show in CSS IntelliSense The css-scheme.xml file often includes a browser token without a version number, to either mean all versions, or perhaps that the version number is unknown. This is common for Chrome as it came into existence after many versions of Safari, and I followed that pattern for Edge (using E, rather than E12).
These browser do not show up in the CSS IntelliSense.
Steps to repo:
Start typing :corner-present
Expected:
(Chrome, Safari 5)
Actual:
(Safari 5).
I could fix this for Edge by changing all E's to E12, but for Chrome it would be a lot of research to see if only "C" is listed because it is since Chrome 1 or if it is because the version is unknown. BrowserStack only goes back to Chrome14.
| 204 |
[] |
0
|
False
|
|
1221
|
[css] generate_browser.js doesn't included MIT copyright when generating browsersjs
|
2015-12-12 11:44:17+00:00
|
2015-12-16 10:48:42+00:00
|
It just includes the MS copyright.
|
completed
|
[css] generate_browser.js doesn't included MIT copyright when generating browsersjs It just includes the MS copyright.
| 31 |
[] |
0
|
False
|
|
1220
|
[css] Fix linear-gradient() snippet syntax
|
2015-12-12 11:31:37+00:00
|
2015-12-16 10:32:15+00:00
|
- corrected the unprefixed syntax
- Moved the -moz- property below the webkit ones, so that all the mid period syntaxes are together and the prefixes follow the recommended webkit -> moz -> ms (not included here) -> o (also not included) -> unprefixed order.
Fixes #1219
|
[css] Fix linear-gradient() snippet syntax - corrected the unprefixed syntax
- Moved the -moz- property below the webkit ones, so that all the mid period syntaxes are together and the prefixes follow the recommended webkit -> moz -> ms (not included here) -> o (also not included) -> unprefixed order.
Fixes #1219
| 92 |
[] |
0
|
False
|
||
1213
|
tsd mocha does not apply to files past index.js
|
2015-12-11 22:40:46+00:00
|
2015-12-20 01:14:02+00:00
|
The mocha file for tsd works correctly for the index.js file that is at the root level of the test folder.
Any nested files within the test folder, as well as any files that are siblings to index.js does not hide the green underline that shows "can't find it" or "can't find describe".
Expected that when installing the tsd mocha, that visual studio code should recognize the commands past the initial index.js file within the test directory.
|
completed
|
tsd mocha does not apply to files past index.js The mocha file for tsd works correctly for the index.js file that is at the root level of the test folder.
Any nested files within the test folder, as well as any files that are siblings to index.js does not hide the green underline that shows "can't find it" or "can't find describe".
Expected that when installing the tsd mocha, that visual studio code should recognize the commands past the initial index.js file within the test directory.
| 126 |
[] |
0
|
False
|
|
1210
|
Open file dialog should start in the directory for the current active file
|
2015-12-11 22:06:42+00:00
|
2016-05-30 16:10:06+00:00
|
When using `File > Open File`, this will open the directory of the last file selected through `File > Open File`. This is sub-optimal, since the current active file may not have been opened through that dialog. The dialog itself should be context-aware.
|
completed
|
Open file dialog should start in the directory for the current active file When using `File > Open File`, this will open the directory of the last file selected through `File > Open File`. This is sub-optimal, since the current active file may not have been opened through that dialog. The dialog itself should be context-aware.
| 75 |
[] |
0
|
False
|
|
1197
|
Weird flashing when hovering
|
2015-12-11 12:27:00+00:00
|
2016-01-27 17:22:54+00:00
|
- theme: Quite Light
- double click on `TO_STRING_MAP` in `keyCodes.ts`
- hover over various instances.
|
completed
|
Weird flashing when hovering - theme: Quite Light
- double click on `TO_STRING_MAP` in `keyCodes.ts`
- hover over various instances.
| 99 |
[] |
0
|
False
|
|
1196
|
[Cancel] buttom should in [Don't Save] buttom's right
|
2015-12-11 12:18:56+00:00
|
2015-12-11 16:48:41+00:00
|
In version 0.10.3, order like this:
This is different from other app:
|
completed
|
[Cancel] buttom should in [Don't Save] buttom's right In version 0.10.3, order like this:
This is different from other app:
| 149 |
[] |
0
|
False
|
|
1193
|
Mac: Keybinding conflicts detected
|
2015-12-11 11:21:37+00:00
|
2015-12-11 16:43:08+00:00
|
With latest I see this:
Conflict detected, command `cursorBottom` cannot be triggered by cmd+down
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorTop` cannot be triggered by cmd+up
//Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js:196 [Plugin Host] debugger listening on port 5870
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorBottom` cannot be triggered by cmd+down
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorTop` cannot be triggered by cmd+up
|
completed
|
Mac: Keybinding conflicts detected With latest I see this:
Conflict detected, command `cursorBottom` cannot be triggered by cmd+down
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorTop` cannot be triggered by cmd+up
//Users/bpasero/Development/monaco/out/vs/workbench/services/thread/electron-browser/threadService.js:196 [Plugin Host] debugger listening on port 5870
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorBottom` cannot be triggered by cmd+down
//Users/bpasero/Development/monaco/out/vs/platform/keybinding/common/commonKeybindingResolver.js:70 Conflict detected, command `cursorTop` cannot be triggered by cmd+up
| 276 |
[] |
0
|
False
|
|
1190
|
Bad suggestion sorting for TS compared to JS
|
2015-12-11 10:09:33+00:00
|
2016-01-19 09:52:40+00:00
|
Going for the for loop snippet:
## JavaScript (snippet is close by):
## TypeScript (snippet is after many non relevant suggestions):
|
completed
|
Bad suggestion sorting for TS compared to JS Going for the for loop snippet:
## JavaScript (snippet is close by):
## TypeScript (snippet is after many non relevant suggestions):
| 150 |
[] |
0
|
False
|
|
1185
|
.ts and .d.ts files sharing the same filename interfere with each other
|
2015-12-11 05:41:17+00:00
|
2015-12-11 22:08:12+00:00
|
I have an in-house library written in TypeScript. It consists of two files: `promises.ts` and a `promises.d.ts` exposing related interfaces globally. The TypeScript compiler has no problem with this setup, and neither does IntelliJ, but VSCode seems to only "be aware" of the `promises.d.ts` content while I have it open as the active file. As soon as I close it or switch to another file, the interfaces declared in `promises.d.ts` get flagged as unknown.
I have seen this on two different computers running VSCode. Both VSCode installations are currenty up to date. It also happens with other libraries using the same naming pattern.
We are not using TypeScript's "generate declaration files" setting.
|
completed
|
.ts and .d.ts files sharing the same filename interfere with each other I have an in-house library written in TypeScript. It consists of two files: `promises.ts` and a `promises.d.ts` exposing related interfaces globally. The TypeScript compiler has no problem with this setup, and neither does IntelliJ, but VSCode seems to only "be aware" of the `promises.d.ts` content while I have it open as the active file. As soon as I close it or switch to another file, the interfaces declared in `promises.d.ts` get flagged as unknown.
I have seen this on two different computers running VSCode. Both VSCode installations are currenty up to date. It also happens with other libraries using the same naming pattern.
We are not using TypeScript's "generate declaration files" setting.
| 210 |
[] |
0
|
False
|
|
1180
|
Allow variables in launch.json config
|
2015-12-10 22:16:28+00:00
|
2015-12-18 10:47:16+00:00
|
Allowing a variable like '${file}', in "launch.json" would open up nice workflows.
For example, I want to launch the debugger with the current file as a parameter, so that I can run a specific test.
Right now, I need to modify the launch.config every time I want to debug a single test.
|
completed
|
Allow variables in launch.json config Allowing a variable like '${file}', in "launch.json" would open up nice workflows.
For example, I want to launch the debugger with the current file as a parameter, so that I can run a specific test.
Right now, I need to modify the launch.config every time I want to debug a single test.
| 95 |
[] |
0
|
False
|
|
1175
|
[python] strings in dictionary values incorrectly highlighted
|
2015-12-10 20:11:55+00:00
|
2015-12-11 09:02:16+00:00
|
When creating dictionaries with any values the strings in the value section are all hi-lighted blue and not red.
e.g. for the following code snippet
``` python
{"a":{"b":"c"}}
```
The string "a" will be highlighted red, while "b" and "c" will be highlighted blue even though they are both strings like "a" is. "b" is also a key to a dict like "a" is
Note: this is using the "Light" theme
|
completed
|
[python] strings in dictionary values incorrectly highlighted When creating dictionaries with any values the strings in the value section are all hi-lighted blue and not red.
e.g. for the following code snippet
``` python
{"a":{"b":"c"}}
```
The string "a" will be highlighted red, while "b" and "c" will be highlighted blue even though they are both strings like "a" is. "b" is also a key to a dict like "a" is
Note: this is using the "Light" theme
| 139 |
[] |
0
|
False
|
|
1171
|
"Change all Occurrences" in a string with stop or whitespace chars
|
2015-12-10 15:28:31+00:00
|
2016-01-06 08:21:59+00:00
|
"Change all Occurrences" doesn't work if the text selection contains stops, spaces or such. Furthermore, if the text was selected from L->R - it just doesn't do anything, but if R->L - it automatically selects the most left word and then invokes the "Change all Occurrences".
|
completed
|
"Change all Occurrences" in a string with stop or whitespace chars "Change all Occurrences" doesn't work if the text selection contains stops, spaces or such. Furthermore, if the text was selected from L->R - it just doesn't do anything, but if R->L - it automatically selects the most left word and then invokes the "Change all Occurrences".
| 100 |
[] |
0
|
False
|
|
1163
|
Document Range Formatting fails
|
2015-12-10 09:46:35+00:00
|
2015-12-10 11:46:16+00:00
|
Steps:
- extension that registers a document and a document range formatting provider
- open a test workspace that activates the extension and trigger a range format.
You get:
```
i.formatRange is not a function: TypeError: i.formatRange is not a function
at Object.u [as formatRange] (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1579:7171)
at t.run (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1579:12653)
at file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1598:17974
at __dirname.undefined.t.Class.define.then (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1544:7415)
at e.showContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1598:17232)
at e._doShowContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:25279)
at e.showContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:24190)
at e._onContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:23875)
at Array.<anonymous> (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:22955)
at t.e._emitToSpecificTypeListeners (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1548:10228)
```
|
completed
|
Document Range Formatting fails Steps:
- extension that registers a document and a document range formatting provider
- open a test workspace that activates the extension and trigger a range format.
You get:
```
i.formatRange is not a function: TypeError: i.formatRange is not a function
at Object.u [as formatRange] (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1579:7171)
at t.run (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1579:12653)
at file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1598:17974
at __dirname.undefined.t.Class.define.then (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1544:7415)
at e.showContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1598:17232)
at e._doShowContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:25279)
at e.showContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:24190)
at e._onContextMenu (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:23875)
at Array.<anonymous> (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1578:22955)
at t.e._emitToSpecificTypeListeners (file:///C:/Program Files (x86)/Visual Studio Code/resources/app/out/vs/workbench/workbench.main.js:1548:10228)
```
| 613 |
[] |
0
|
False
|
|
1162
|
Workspace UI storage not picked up when launching workspace with different casing
|
2015-12-10 08:56:23+00:00
|
2016-09-22 12:54:31+00:00
|
Currently we loose all workspace associated state when the workspace path is using different casing. Ideally the storage is agnostic to casing for file systems that are case insensitive.
|
completed
|
Workspace UI storage not picked up when launching workspace with different casing Currently we loose all workspace associated state when the workspace path is using different casing. Ideally the storage is agnostic to casing for file systems that are case insensitive.
| 60 |
[] |
0
|
False
|
|
1160
|
Cannot read property 'highlightSpans' of undefined
|
2015-12-10 08:19:56+00:00
|
2015-12-14 11:55:07+00:00
|
Useless stack trace:
```
Cannot read property 'highlightSpans' of undefined
e.doShow @ workbench.main.js:1598
```
Reproduction code (TypeScript):
``` ts
function a() {
let b = {{
a: 'string'
};
}
```
Expected: No fatal error in engine
Actual: Fatal error caused by `b = {{` inside function.
Version: 0.10.3 Mac OS X
|
completed
|
Cannot read property 'highlightSpans' of undefined Useless stack trace:
```
Cannot read property 'highlightSpans' of undefined
e.doShow @ workbench.main.js:1598
```
Reproduction code (TypeScript):
``` ts
function a() {
let b = {{
a: 'string'
};
}
```
Expected: No fatal error in engine
Actual: Fatal error caused by `b = {{` inside function.
Version: 0.10.3 Mac OS X
| 115 |
[] |
0
|
False
|
|
1157
|
Introducing '.js' file causes errors with TypeScript code
|
2015-12-10 01:46:49+00:00
|
2015-12-15 15:52:11+00:00
|
From https://www.reddit.com/r/programming/comments/3ux8fs/announcing_typescript_17/cxo5ldn?context=3.
> I just updated VSCode to the latest version (0.10.3) and reduced this problem to a small case, and I'm really confused:
> 1. A simple internal module, a simple .d.ts referencing it. Everything works fine: http://i.imgur.com/O8uIQFT.png
2. I create a plain .js file. Even without writing to it or saving it again, I get Schrodinger's interface: http://i.imgur.com/siOf1AV.png
> At this point, the errors about the interface file won't go away. After I close the .js file in the editor, close the folder, and reopen the folder, things go back to normal. But as soon as I open a plain .js file, they come back just like before. After the errors get triggered, I can close the .js file and they stay in the status bar. If I then add both the module and the .d.ts to the "working files" list, then remove .d.ts from it, the errors vanish again.
We're not sure what sort of interaction might be going on with the TypeScript language service, so we felt it would be better filed here.
|
completed
|
Introducing '.js' file causes errors with TypeScript code From https://www.reddit.com/r/programming/comments/3ux8fs/announcing_typescript_17/cxo5ldn?context=3.
> I just updated VSCode to the latest version (0.10.3) and reduced this problem to a small case, and I'm really confused:
> 1. A simple internal module, a simple .d.ts referencing it. Everything works fine: http://i.imgur.com/O8uIQFT.png
2. I create a plain .js file. Even without writing to it or saving it again, I get Schrodinger's interface: http://i.imgur.com/siOf1AV.png
> At this point, the errors about the interface file won't go away. After I close the .js file in the editor, close the folder, and reopen the folder, things go back to normal. But as soon as I open a plain .js file, they come back just like before. After the errors get triggered, I can close the .js file and they stay in the status bar. If I then add both the module and the .d.ts to the "working files" list, then remove .d.ts from it, the errors vanish again.
We're not sure what sort of interaction might be going on with the TypeScript language service, so we felt it would be better filed here.
| 373 |
[] |
0
|
False
|
|
1151
|
Recent Folders should not be case sensitive in Windows
|
2015-12-09 23:23:58+00:00
|
2015-12-16 15:43:52+00:00
|
Since Windows is not case sensitive_ for Files and Folders, the recent folders should also not to be.
If you open a folder in Code via command line, with different case, it adds a new entry for each one. It also maintain a _folder state_ (like the files that are opened in that folder) different for each entry.
Opening **Code** with different case:
It adds 3 different entries in **Menu**
And also in **Command Palette**:
|
completed
|
Recent Folders should not be case sensitive in Windows Since Windows is not case sensitive_ for Files and Folders, the recent folders should also not to be.
If you open a folder in Code via command line, with different case, it adds a new entry for each one. It also maintain a _folder state_ (like the files that are opened in that folder) different for each entry.
Opening **Code** with different case:
It adds 3 different entries in **Menu**
And also in **Command Palette**:
| 302 |
[] |
0
|
False
|
|
1150
|
[json] 'postbuild' and 'prebuild' scripts are missing from hints for ASP.NET project.json
|
2015-12-09 22:23:56+00:00
|
2015-12-11 15:59:28+00:00
|
For some reason the `postbuild` and `prebuild` scripts are missing from hints shown for `project.json` in editor:
The same `prebuild` script in Atom:
The current schema:
http://json.schemastore.org/project
I cannot yet trace where there is a provider of that content. I've only found that current provider also seems to be missing that properties:
https://github.com/Microsoft/vscode/blob/468635529ed0e10f1aeffee31ee2327e76051b05/src/vs/editor/browser/standalone/standaloneSchemas.ts#L391-L405
Thanks!
VSCode: 10.3
OS X: 10.10
|
completed
|
[json] 'postbuild' and 'prebuild' scripts are missing from hints for ASP.NET project.json For some reason the `postbuild` and `prebuild` scripts are missing from hints shown for `project.json` in editor:
The same `prebuild` script in Atom:
The current schema:
http://json.schemastore.org/project
I cannot yet trace where there is a provider of that content. I've only found that current provider also seems to be missing that properties:
https://github.com/Microsoft/vscode/blob/468635529ed0e10f1aeffee31ee2327e76051b05/src/vs/editor/browser/standalone/standaloneSchemas.ts#L391-L405
Thanks!
VSCode: 10.3
OS X: 10.10
| 298 |
[] |
0
|
False
|
|
1148
|
[json] Provide full documented json schema
|
2015-12-09 20:56:32+00:00
|
2015-12-10 14:37:33+00:00
|
The configuration contribution point offers a great chance to provide a rich documentation about the JsonSchema, [yet it simply refers to the official meta-schema](https://github.com/Microsoft/vscode/blob/468635529ed0e10f1aeffee31ee2327e76051b05/src/vs/platform/configuration/common/configurationRegistry.ts#L110) that does not contain any useful description.
If you say, that this is something you would merge into VS Code, I would start the implementation and open a PR. Implementation details:
1. Create a new file containing the complete meta-schema in Typescript with descriptions.
2. Import the schema and register it with `PluginsRegistry.registerExtensionPoint<IConfigurationNode>(...)`.
|
completed
|
[json] Provide full documented json schema The configuration contribution point offers a great chance to provide a rich documentation about the JsonSchema, [yet it simply refers to the official meta-schema](https://github.com/Microsoft/vscode/blob/468635529ed0e10f1aeffee31ee2327e76051b05/src/vs/platform/configuration/common/configurationRegistry.ts#L110) that does not contain any useful description.
If you say, that this is something you would merge into VS Code, I would start the implementation and open a PR. Implementation details:
1. Create a new file containing the complete meta-schema in Typescript with descriptions.
2. Import the schema and register it with `PluginsRegistry.registerExtensionPoint<IConfigurationNode>(...)`.
| 201 |
[] |
0
|
False
|
|
1146
|
Tasks not showing up in Command Palette
|
2015-12-09 19:27:10+00:00
|
2016-01-28 11:48:22+00:00
|
Tested using windows version
|
completed
|
Tasks not showing up in Command Palette Tested using windows version
| 17 |
[] |
0
|
False
|
|
1141
|
Reloading Extension Host window doesn't restart debug session
|
2015-12-09 16:40:12+00:00
|
2015-12-11 14:50:05+00:00
|
- create TypeScript extension
- F5
- reload EH window (Cmd-R)
Observe: VSCode debugger doesn't attach to EH
BTW, an "Open file" in the EH works fine.
|
completed
|
Reloading Extension Host window doesn't restart debug session - create TypeScript extension
- F5
- reload EH window (Cmd-R)
Observe: VSCode debugger doesn't attach to EH
BTW, an "Open file" in the EH works fine.
| 64 |
[] |
0
|
False
|
|
1140
|
Backspace stops prematurely
|
2015-12-09 16:14:57+00:00
|
2016-01-27 16:47:09+00:00
|
With the selected area, I would expect it all to be removed to the given point, but instead, it only removes the parenthesis. Happens when I tested this with both Java and Javascript.
Before backspace:
After pressing backspace:
Expected:
|
completed
|
Backspace stops prematurely With the selected area, I would expect it all to be removed to the given point, but instead, it only removes the parenthesis. Happens when I tested this with both Java and Javascript.
Before backspace:
After pressing backspace:
Expected:
| 231 |
[] |
0
|
False
|
|
1139
|
Intellisense completely hosed on files with names starting with "temp"
|
2015-12-09 14:12:23+00:00
|
2015-12-09 16:15:09+00:00
|
I have a javascript node project with some TypeScript definition files inside it. My jsconfig.json is as follows:
{
"compilerOptions": {
"target": "ES6",
"module": "commonjs"
}
}
If I rename a javascript source file to temp_hello.js or even temple.js (imagine if temples were in my business domain!) then the intellisense stops working for the file (it does not pick up anything in the typescript definition files) and it also forgets my jsconfig.json settings. That means I can't use ES6 syntax anymore!
|
completed
|
Intellisense completely hosed on files with names starting with "temp" I have a javascript node project with some TypeScript definition files inside it. My jsconfig.json is as follows:
{
"compilerOptions": {
"target": "ES6",
"module": "commonjs"
}
}
If I rename a javascript source file to temp_hello.js or even temple.js (imagine if temples were in my business domain!) then the intellisense stops working for the file (it does not pick up anything in the typescript definition files) and it also forgets my jsconfig.json settings. That means I can't use ES6 syntax anymore!
| 160 |
[] |
0
|
False
|
|
1138
|
Error pushing to git remote with http
|
2015-12-09 13:37:38+00:00
|
2016-04-18 07:02:22+00:00
|
I have configured my git remote like this:
```
[remote "origin"]
url = http://MY-HOST.../branch-locatlocator-select-ui.git
```
And when i do a push show me an error:
```
fatal: Authentication failed for 'http://MY-HOST.../branch-locatlocator-select-ui.git/'
```
Why Visual Studio Code add the final slash? :(
|
completed
|
Error pushing to git remote with http I have configured my git remote like this:
```
[remote "origin"]
url = http://MY-HOST.../branch-locatlocator-select-ui.git
```
And when i do a push show me an error:
```
fatal: Authentication failed for 'http://MY-HOST.../branch-locatlocator-select-ui.git/'
```
Why Visual Studio Code add the final slash? :(
| 114 |
[] |
0
|
False
|
|
1125
|
Change defaults for tabSize, insertSpaces
|
2015-12-09 09:42:56+00:00
|
2015-12-09 09:51:46+00:00
|
We have received a lot of feedback on twitter about how the current default values `tabSize: "auto"` and `insertSpaces: "auto"` lead to confusion.
The reason is that these values mean that the settings will be "gussed" based on the current opened file. The guessing code is limited in cases where the file does not give sufficient hints and causes surprise to end users when some files resolve to `insertSpaces: true` and some to `insertSpaces: false` in a seemingly unpredictable manner.
We have decided to change the defaults to `tabSize: 4, insertSpaces: true` as this seems to be the most common used setting and because most of the compilers can handle spaces, while some compilers do not like tabs.
|
completed
|
Change defaults for tabSize, insertSpaces We have received a lot of feedback on twitter about how the current default values `tabSize: "auto"` and `insertSpaces: "auto"` lead to confusion.
The reason is that these values mean that the settings will be "gussed" based on the current opened file. The guessing code is limited in cases where the file does not give sufficient hints and causes surprise to end users when some files resolve to `insertSpaces: true` and some to `insertSpaces: false` in a seemingly unpredictable manner.
We have decided to change the defaults to `tabSize: 4, insertSpaces: true` as this seems to be the most common used setting and because most of the compilers can handle spaces, while some compilers do not like tabs.
| 192 |
[] |
0
|
False
|
|
1121
|
Markdown Inline Formats in Headings doesn't themed correctly
|
2015-12-09 08:34:47+00:00
|
2016-09-26 17:35:25+00:00
|
In Markdown preview, inline formats in single backticks (`) seems small sized in heading. Headings of different sizes have this problem in common.
|
completed
|
Markdown Inline Formats in Headings doesn't themed correctly In Markdown preview, inline formats in single backticks (`) seems small sized in heading. Headings of different sizes have this problem in common.
| 110 |
[] |
0
|
False
|
|
1120
|
TAB should not indent empty lines in a multi-line selection
|
2015-12-09 08:31:03+00:00
|
2015-12-09 10:11:35+00:00
|
1. Start with the document:
```
a
b
c
```
2. Select the entire text
3. Press <kbd>TAB</kbd>
Expected: The three lines with text get indented. The empty third line remains unindented.
```
a
b
c
```
Actual: All the four lines get indented, and I then have to manually delete the trailing whitespace from the third line.
```
a
b
c
```
(This is only when indenting a multi-line selection; when pressing TAB in an empty line then the line _should_ get indented as it currently does.)
|
completed
|
TAB should not indent empty lines in a multi-line selection 1. Start with the document:
```
a
b
c
```
2. Select the entire text
3. Press <kbd>TAB</kbd>
Expected: The three lines with text get indented. The empty third line remains unindented.
```
a
b
c
```
Actual: All the four lines get indented, and I then have to manually delete the trailing whitespace from the third line.
```
a
b
c
```
(This is only when indenting a multi-line selection; when pressing TAB in an empty line then the line _should_ get indented as it currently does.)
| 149 |
[] |
0
|
False
|
|
1117
|
Avoid 3x file size memory pressure when resolving file contents
|
2015-12-09 04:24:21+00:00
|
2015-12-21 07:33:24+00:00
|
open a file size 96935KB error:
Visual Studio Code has crashed
We are sorry for the inconvenience! Please restart Visual Studio Code.
|
completed
|
Avoid 3x file size memory pressure when resolving file contents open a file size 96935KB error:
Visual Studio Code has crashed
We are sorry for the inconvenience! Please restart Visual Studio Code.
| 50 |
[] |
0
|
False
|
|
1112
|
Quick info gets cut off for long text
|
2015-12-08 20:50:16+00:00
|
2015-12-09 09:14:55+00:00
|
|
completed
|
Quick info gets cut off for long text 
| 60 |
[] |
0
|
False
|
|
1111
|
Extensions: Upgrading Extensions Blows Up
|
2015-12-08 20:01:16+00:00
|
2015-12-16 16:34:30+00:00
|
I pushed out a new version of the Vim extension, however, when upgrading it on top of the existing version, we are seeing this error: https://github.com/VSCodeVim/Vim/issues/93. Installing the new version by itself (with no previous versions of the Vim extension) works successfully.
I've been unsuccessful at getting a repro. Is there a way in which I can install a specific version from the marketplace?
I've built the packages (`vsce package`) and made them available here: https://github.com/VSCodeVim/Vim/releases. I have tried:
1) `code vim-0.0.2.vsix` - This installs successfully
2) On top of the existing install `code vim-0.0.3.vsix`, VSCode blows up with a different error than reported in https://github.com/VSCodeVim/Vim/issues/93. The [console log is here](https://github.com/Microsoft/vscode/files/55978/vscode-blows-up.txt).
3) Installing `code vim-0.0.3.vsix` (not upgrading) works fine
tldr;
- Is there a way to install a specific version of an extension from the marketplace?
- Barring the above, is manually upgrading a plugin through the vsix expected to work?
|
completed
|
Extensions: Upgrading Extensions Blows Up I pushed out a new version of the Vim extension, however, when upgrading it on top of the existing version, we are seeing this error: https://github.com/VSCodeVim/Vim/issues/93. Installing the new version by itself (with no previous versions of the Vim extension) works successfully.
I've been unsuccessful at getting a repro. Is there a way in which I can install a specific version from the marketplace?
I've built the packages (`vsce package`) and made them available here: https://github.com/VSCodeVim/Vim/releases. I have tried:
1) `code vim-0.0.2.vsix` - This installs successfully
2) On top of the existing install `code vim-0.0.3.vsix`, VSCode blows up with a different error than reported in https://github.com/VSCodeVim/Vim/issues/93. The [console log is here](https://github.com/Microsoft/vscode/files/55978/vscode-blows-up.txt).
3) Installing `code vim-0.0.3.vsix` (not upgrading) works fine
tldr;
- Is there a way to install a specific version of an extension from the marketplace?
- Barring the above, is manually upgrading a plugin through the vsix expected to work?
| 325 |
[] |
0
|
False
|
|
1098
|
Cmd+O proposes wrong folder
|
2015-12-08 09:25:03+00:00
|
2015-12-08 12:28:35+00:00
|
- be on mac
- git cmd+o
- > it open with the folder that you have opened last (like, `~/dev/vscode`) which is never a good choice because why would I open the folder which I opened last again? Instead it should open the folder from which I have opened the last folder (the parent of the current folder, `~/dev/`)
|
completed
|
Cmd+O proposes wrong folder - be on mac
- git cmd+o
- > it open with the folder that you have opened last (like, `~/dev/vscode`) which is never a good choice because why would I open the folder which I opened last again? Instead it should open the folder from which I have opened the last folder (the parent of the current folder, `~/dev/`)
| 93 |
[] |
0
|
False
|
|
1095
|
Failed to install an extension with EPERM exception (operation not permitted, write)
|
2015-12-08 07:42:56+00:00
|
2015-12-14 09:26:18+00:00
|
This seems to happen on Windows only using Commit 942e9b and could be reproduced on multiple machines.
- wanted to install tslint
- checked whether it was already installed ant tslint didn't show up
- selecting tslint from `install extension`
-> EENOPERM exception
|
completed
|
Failed to install an extension with EPERM exception (operation not permitted, write) This seems to happen on Windows only using Commit 942e9b and could be reproduced on multiple machines.
- wanted to install tslint
- checked whether it was already installed ant tslint didn't show up
- selecting tslint from `install extension`
-> EENOPERM exception
| 89 |
[] |
0
|
False
|
|
1094
|
Mac: TypeScript language service fails
|
2015-12-08 07:09:43+00:00
|
2015-12-15 08:17:37+00:00
|
I think since the update to 1.7 the language service stops working for me quickly. The ts server is still running but no smartness comes from the editor. Is there a way to enable diagnostics to find out what is happening?
|
completed
|
Mac: TypeScript language service fails I think since the update to 1.7 the language service stops working for me quickly. The ts server is still running but no smartness comes from the editor. Is there a way to enable diagnostics to find out what is happening?
| 59 |
[] |
0
|
False
|
|
1078
|
Debug mode, the value of the variable error
|
2015-12-07 17:07:15+00:00
|
2016-07-06 14:17:23+00:00
|
Hi~
in the function b, the paramether id is a string 'id from middleware'. but vs code tell me it's a object and equal to the second parameter.
I think the pictures is more intuitive. beg your pardon for my English. T T
https://c.hime.io/images/L0o.png
``` javascript
'use strict';
const koa = require('koa');
const app = koa();
function* b(id, {
age,
name = 'name from b'
}) {
console.log(id);
return {
id: id,
name: name,
age: age
}
}
app.use(function* () {
let {
age: returnB
} = yield* b('id from middleware', {
age: 25
});
this.body = 'returnB(age):' + returnB;
});
app.listen(3001);
```
|
completed
|
Debug mode, the value of the variable error Hi~
in the function b, the paramether id is a string 'id from middleware'. but vs code tell me it's a object and equal to the second parameter.
I think the pictures is more intuitive. beg your pardon for my English. T T
https://c.hime.io/images/L0o.png
``` javascript
'use strict';
const koa = require('koa');
const app = koa();
function* b(id, {
age,
name = 'name from b'
}) {
console.log(id);
return {
id: id,
name: name,
age: age
}
}
app.use(function* () {
let {
age: returnB
} = yield* b('id from middleware', {
age: 25
});
this.body = 'returnB(age):' + returnB;
});
app.listen(3001);
```
| 213 |
[] |
0
|
False
|
|
1064
|
closing semicolon emmet expansion SCSS
|
2015-12-07 09:17:10+00:00
|
2015-12-16 08:09:35+00:00
|
When you expand an emmet expression in .SCSS files, a semicolon is not added at the end. I search everywhere, but I can not find this in settings. So I'm filing this as a bug.
|
completed
|
closing semicolon emmet expansion SCSS When you expand an emmet expression in .SCSS files, a semicolon is not added at the end. I search everywhere, but I can not find this in settings. So I'm filing this as a bug.
| 65 |
[] |
0
|
False
|
|
1052
|
Incorrect error in TypeScript code
|
2015-12-06 18:52:56+00:00
|
2015-12-08 11:41:41+00:00
|
I'm using version df352367df2efcfa9d602d471e4e2f42140a0f05
For this code I get an incorrect error.
``` typescript
/**
* Removes all the children from `<div class="children"></div>` element
*
*/
removeChildren() {
if (this.element.querySelector('div.children')) {
this.element.removeChild(this.element.querySelector('div.children'));
}
}
```
TypeScript compiler does not complain for this code but VSCode throws this error:
<img width="1199" alt="cap" src="https://cloud.githubusercontent.com/assets/543633/11614942/575d0dae-9c07-11e5-8caf-7dd6da702b20.png">
|
completed
|
Incorrect error in TypeScript code I'm using version df352367df2efcfa9d602d471e4e2f42140a0f05
For this code I get an incorrect error.
``` typescript
/**
* Removes all the children from `<div class="children"></div>` element
*
*/
removeChildren() {
if (this.element.querySelector('div.children')) {
this.element.removeChild(this.element.querySelector('div.children'));
}
}
```
TypeScript compiler does not complain for this code but VSCode throws this error:
<img width="1199" alt="cap" src="https://cloud.githubusercontent.com/assets/543633/11614942/575d0dae-9c07-11e5-8caf-7dd6da702b20.png">
| 214 |
[] |
0
|
False
|
|
1048
|
html, editor.autoClosingBrackets doesn't work well
|
2015-12-06 06:34:59+00:00
|
2017-03-31 09:02:46+00:00
|
When I am typing a html file and adding a class to a tag such as :
`<div class="some-class"></div>`
when I type `class="`, the double quotes doesn't auto closing.
editor.autoClosingBrackets doesn't work well when cursor in `<...>`
|
completed
|
html, editor.autoClosingBrackets doesn't work well When I am typing a html file and adding a class to a tag such as :
`<div class="some-class"></div>`
when I type `class="`, the double quotes doesn't auto closing.
editor.autoClosingBrackets doesn't work well when cursor in `<...>`
| 94 |
[] |
0
|
False
|
|
1047
|
Typescript: breakpoints on the first statement of a static method don't work
|
2015-12-06 06:31:59+00:00
|
2015-12-16 10:27:45+00:00
|
Hey,
I found a minor issue with typescript debugging. When executing a typescript program, breakpoints placed on the first line of static methods are moved to the closing brace of the method.
For example:
``` typescript
import fs = require('fs');
class MyClass {
public static doSomethingStatic(): void {
let a: boolean = fs.existsSync('a');
let b: boolean = fs.existsSync('b');
let c: boolean = fs.existsSync('c');
}
}
MyClass.doSomethingStatic();
```
Breakpoints on line `b`, `c` work as expected, but putting a breakpoint on line `a` does not work: the breakpoint gets moved to the closing brace `}`.
The problem is not present in non-static methods.
|
completed
|
Typescript: breakpoints on the first statement of a static method don't work Hey,
I found a minor issue with typescript debugging. When executing a typescript program, breakpoints placed on the first line of static methods are moved to the closing brace of the method.
For example:
``` typescript
import fs = require('fs');
class MyClass {
public static doSomethingStatic(): void {
let a: boolean = fs.existsSync('a');
let b: boolean = fs.existsSync('b');
let c: boolean = fs.existsSync('c');
}
}
MyClass.doSomethingStatic();
```
Breakpoints on line `b`, `c` work as expected, but putting a breakpoint on line `a` does not work: the breakpoint gets moved to the closing brace `}`.
The problem is not present in non-static methods.
| 228 |
[] |
0
|
False
|
|
1041
|
JS: default object functin param show error in editor
|
2015-12-05 16:44:11+00:00
|
2015-12-07 10:41:24+00:00
|
such as: a & b will show error tip
``` js
function test({a = "foo", b = "bar"} = {}) {
console.log(a + " " + b);
}
```
|
completed
|
JS: default object functin param show error in editor such as: a & b will show error tip
``` js
function test({a = "foo", b = "bar"} = {}) {
console.log(a + " " + b);
}
```
| 66 |
[] |
0
|
False
|
|
1034
|
JavaScript language support reports assignment to function as error instead of warning
|
2015-12-05 01:48:12+00:00
|
2016-03-14 08:48:32+00:00
|
This is a holdover from TS language service errors.
|
completed
|
JavaScript language support reports assignment to function as error instead of warning This is a holdover from TS language service errors.
| 78 |
[] |
0
|
False
|
|
1033
|
Locally exported environment variables are overwritten by ~/.bash_profile when using `code .`
|
2015-12-05 00:48:18+00:00
|
2016-04-28 14:34:22+00:00
|
Per https://github.com/Microsoft/vscode-go/issues/141, there appears to still be an issue with how env vars are passed into Code, even after the fix for https://github.com/Microsoft/vscode/issues/560.
Steps to reproduce:
1. have `export FOO=1` in your `.bash_profile`
2. ensure your function to start visual studio code looks like this `code () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $* ;}`
3. open a terminal session
4. `export FOO=2` in your terminal session
5. open `code .`
6. open developer tools, and eval `process.env["FOO"]`
Expected: `Foo` should be `2`
Result: `FOO` will be `1`
But the thing that's really odd is that if you skip step (1) (remove this from you `.bash_profile`), you will see `Foo` set to `2`. So in that case, the local environment is getting passed in.
It seems like this must be either a problem with how vscode is setting up the env vars, or how `open` in OS X behaves.
|
completed
|
Locally exported environment variables are overwritten by ~/.bash_profile when using `code .` Per https://github.com/Microsoft/vscode-go/issues/141, there appears to still be an issue with how env vars are passed into Code, even after the fix for https://github.com/Microsoft/vscode/issues/560.
Steps to reproduce:
1. have `export FOO=1` in your `.bash_profile`
2. ensure your function to start visual studio code looks like this `code () { VSCODE_CWD="$PWD" open -n -b "com.microsoft.VSCode" --args $* ;}`
3. open a terminal session
4. `export FOO=2` in your terminal session
5. open `code .`
6. open developer tools, and eval `process.env["FOO"]`
Expected: `Foo` should be `2`
Result: `FOO` will be `1`
But the thing that's really odd is that if you skip step (1) (remove this from you `.bash_profile`), you will see `Foo` set to `2`. So in that case, the local environment is getting passed in.
It seems like this must be either a problem with how vscode is setting up the env vars, or how `open` in OS X behaves.
| 317 |
[] |
0
|
False
|
|
1032
|
Please don't lock the tsconfig.json file
|
2015-12-04 23:30:19+00:00
|
2016-01-29 13:39:37+00:00
|
I am attempting to use a separate git client and it keeps complaining about the tsconfig.json file being locked. If I close the folder from Visual Studio Code, the file is unlocked but also deleted.
It looks like Visual Studio Code is somehow locking the tsconfig.json file.
Expected:
Allow other applications to read and write the tsconfig.json file even if the folder containing that file is open in Visual Studio Code.
Environment:
Visual Studio Code:
OS: Windows 7
|
completed
|
Please don't lock the tsconfig.json file I am attempting to use a separate git client and it keeps complaining about the tsconfig.json file being locked. If I close the folder from Visual Studio Code, the file is unlocked but also deleted.
It looks like Visual Studio Code is somehow locking the tsconfig.json file.
Expected:
Allow other applications to read and write the tsconfig.json file even if the folder containing that file is open in Visual Studio Code.
Environment:
Visual Studio Code:
OS: Windows 7
| 178 |
[] |
0
|
False
|
|
1011
|
Ctrl + click on quick open does not work
|
2015-12-04 11:19:33+00:00
|
2015-12-04 14:38:38+00:00
|
- Open quick open with ctrl + tab
- Click on file you want to open while holding down ctrl - **nothing happens**
- I would expect the file gets opened
I see this on mac el capitan. I think it was working before your promise chain work since I this is part of my workflow.
|
completed
|
Ctrl + click on quick open does not work - Open quick open with ctrl + tab
- Click on file you want to open while holding down ctrl - **nothing happens**
- I would expect the file gets opened
I see this on mac el capitan. I think it was working before your promise chain work since I this is part of my workflow.
| 77 |
[] |
0
|
False
|
|
1008
|
Extensions: Install Extension is slow
|
2015-12-04 09:34:07+00:00
|
2015-12-04 10:35:53+00:00
|
When listing available extensions (typing `ctrl+shift+p`and then `ìnst` and hit `enter`) it takes at least **5 seconds** to display anything.
Meanwhile, there's no user feedback other than an indeterminate loader.
What about having a faster feedback with for example cached results of plugins list while newest plugins list is being retrieved ?
It seems that the more extension are available, the longer it will take to display anything, so it will likely get worse.
|
completed
|
Extensions: Install Extension is slow When listing available extensions (typing `ctrl+shift+p`and then `ìnst` and hit `enter`) it takes at least **5 seconds** to display anything.
Meanwhile, there's no user feedback other than an indeterminate loader.
What about having a faster feedback with for example cached results of plugins list while newest plugins list is being retrieved ?
It seems that the more extension are available, the longer it will take to display anything, so it will likely get worse.
| 126 |
[] |
0
|
False
|
|
1007
|
Quickopen not finding all files
|
2015-12-04 09:28:02+00:00
|
2015-12-04 09:32:00+00:00
|
quickopen, vscode repo, search for some files in quick open does not always give results even though they exist.
Searching for pluginHostMain.ts produces no results for me. Once I open that file manually it starts appearing in quick open.
I see this on OS X el capitan with latest code. Started happening 3 days ago - about the time you messed with that complex promise chain
|
completed
|
Quickopen not finding all files quickopen, vscode repo, search for some files in quick open does not always give results even though they exist.
Searching for pluginHostMain.ts produces no results for me. Once I open that file manually it starts appearing in quick open.
I see this on OS X el capitan with latest code. Started happening 3 days ago - about the time you messed with that complex promise chain
| 96 |
[] |
0
|
False
|
|
1003
|
Suggestion Widget appears to eagerly
|
2015-12-04 08:02:53+00:00
|
2015-12-15 13:32:34+00:00
|
I have custom key bindings like these
```
{ "key": ";", "command": "^acceptSelectedSuggestion", "when": "editorTextFocus && suggestWidgetVisible" },
{ "key": "space", "command": "^acceptSelectedSuggestion", "when": "editorTextFocus && suggestWidgetVisible" },
...
```
to mimic how autocomplete works in the full VS, however, this makes typing something like
```
var foo = 1;
```
difficult in JavaScript/TypeScript because when typing `1`, the suggestion widget eagerly appears with `Int16Array` and hitting `;` autcompletes to it and you end up with
```
var foo = Int16Array;
```
|
completed
|
Suggestion Widget appears to eagerly I have custom key bindings like these
```
{ "key": ";", "command": "^acceptSelectedSuggestion", "when": "editorTextFocus && suggestWidgetVisible" },
{ "key": "space", "command": "^acceptSelectedSuggestion", "when": "editorTextFocus && suggestWidgetVisible" },
...
```
to mimic how autocomplete works in the full VS, however, this makes typing something like
```
var foo = 1;
```
difficult in JavaScript/TypeScript because when typing `1`, the suggestion widget eagerly appears with `Int16Array` and hitting `;` autcompletes to it and you end up with
```
var foo = Int16Array;
```
| 206 |
[] |
0
|
False
|
|
1001
|
No longer responding when opening a big file?
|
2015-12-04 04:37:31+00:00
|
2015-12-07 17:19:22+00:00
|
When I click the file (a 4M JSON file) in the file list panel in the left, the content of this file is correctly displayed but without syntax highlighting. And after that VS Code is no longer responding, I thought it's parsing the file, so I waited for a while. Then it alerts "Visual Studio Code is no longer responding: Exit or Keep waiting".
Windows Task Manager shows it's still "Running" (rather than "Not responding"), but even I select "Keep waiting" and wait for over half an hour, the editor is still no responding.
I thought the JSON file is common, and maybe using a smaller file will also reproduce this issue. If you can't reproduce this issue I'll do some study and try to provide sample.
Windows 7 64bit
|
completed
|
No longer responding when opening a big file? When I click the file (a 4M JSON file) in the file list panel in the left, the content of this file is correctly displayed but without syntax highlighting. And after that VS Code is no longer responding, I thought it's parsing the file, so I waited for a while. Then it alerts "Visual Studio Code is no longer responding: Exit or Keep waiting".
Windows Task Manager shows it's still "Running" (rather than "Not responding"), but even I select "Keep waiting" and wait for over half an hour, the editor is still no responding.
I thought the JSON file is common, and maybe using a smaller file will also reproduce this issue. If you can't reproduce this issue I'll do some study and try to provide sample.
Windows 7 64bit
| 196 |
[] |
0
|
False
|
|
1000
|
Slow response when system is offline
|
2015-12-04 04:20:49+00:00
|
2016-05-10 12:40:38+00:00
|
When system is connected to network but don't have access to internet (just local network) navigation, move , copy , rename in directories and files become very slow. it's happening periodically and seems like it's waiting for kind of timeout.
|
completed
|
Slow response when system is offline When system is connected to network but don't have access to internet (just local network) navigation, move , copy , rename in directories and files become very slow. it's happening periodically and seems like it's waiting for kind of timeout.
| 117 |
[] |
0
|
False
|
|
999
|
Cannot invoke an expression whose type lacks a call signature (versus optional semicolon)
|
2015-12-04 03:45:12+00:00
|
2016-03-14 08:48:24+00:00
|
I am getting the error "Cannot invoke an expression whose type lacks a call signature." on this minimalist js test code (tested with v0.10.2 and v0.10.3):
``` javascript
module.exports = function(env) {
env.deciders = []
require('./test')(env)
}
```
the error is on the underlined code `[]
require('./test')` (with the return, whatever LF or CRLF)
and adding the **optional** semicolon after [] makes the error disappear:
``` javascript
module.exports = function(env) {
env.deciders = [];
require('./test')(env)
}
```
there's no test.js file since it does not matter if it exists or not.
my jsconfig.json file is set for ES6 / commonjs.
|
completed
|
Cannot invoke an expression whose type lacks a call signature (versus optional semicolon) I am getting the error "Cannot invoke an expression whose type lacks a call signature." on this minimalist js test code (tested with v0.10.2 and v0.10.3):
``` javascript
module.exports = function(env) {
env.deciders = []
require('./test')(env)
}
```
the error is on the underlined code `[]
require('./test')` (with the return, whatever LF or CRLF)
and adding the **optional** semicolon after [] makes the error disappear:
``` javascript
module.exports = function(env) {
env.deciders = [];
require('./test')(env)
}
```
there's no test.js file since it does not matter if it exists or not.
my jsconfig.json file is set for ES6 / commonjs.
| 229 |
[] |
0
|
False
|
|
998
|
Explorer should not reopen a file when hiding and showing again
|
2015-12-04 03:39:48+00:00
|
2016-05-27 05:49:12+00:00
|
Don't know if it's bug or feature, but it's different from my experience using Visual Studio Community, so I decided to add it.
Steps to reproduce this:
- Open file in editor
- Close it
- Collapse the Explore tab
- Expand the Explore tab
Result: Previously closed file is open again
|
completed
|
Explorer should not reopen a file when hiding and showing again Don't know if it's bug or feature, but it's different from my experience using Visual Studio Community, so I decided to add it.
Steps to reproduce this:
- Open file in editor
- Close it
- Collapse the Explore tab
- Expand the Explore tab
Result: Previously closed file is open again
| 86 |
[] |
0
|
False
|
|
984
|
tsd for lodash and underscore stopped working
|
2015-12-03 19:25:48+00:00
|
2016-04-28 10:47:49+00:00
|
When I'm installing tsd for underscore or lodash Visual Sudio Code sees the variable that I'm assigning the module to as it is of type any. It correctly interprets it's members parameters, but does not see the members of fist level. Example:
I'm installing my tsd with `tsd install lodash` or `tsd install underscore` command. It works correctly for other libraries like colors or node itself. It just have a problem with those two.
What I found also is that when I open definition file it shows some errors in it.
I would not suspect Visual Studio Code if there will be problem with only one of those libraries, but this is not looking like a coincidence.
|
completed
|
tsd for lodash and underscore stopped working When I'm installing tsd for underscore or lodash Visual Sudio Code sees the variable that I'm assigning the module to as it is of type any. It correctly interprets it's members parameters, but does not see the members of fist level. Example:
I'm installing my tsd with `tsd install lodash` or `tsd install underscore` command. It works correctly for other libraries like colors or node itself. It just have a problem with those two.
What I found also is that when I open definition file it shows some errors in it.
I would not suspect Visual Studio Code if there will be problem with only one of those libraries, but this is not looking like a coincidence.
| 227 |
[] |
0
|
False
|
|
975
|
[python] Add .gn as a python file extension
|
2015-12-03 16:40:16+00:00
|
2015-12-04 07:55:02+00:00
|
GN is a meta-build system that generates NinjaBuild files. GN syntax is a stripped down version of python.
|
[python] Add .gn as a python file extension GN is a meta-build system that generates NinjaBuild files. GN syntax is a stripped down version of python.
| 47 |
[] |
0
|
False
|
||
971
|
Cannot validate the php file. The php program was not found.
|
2015-12-03 15:17:59+00:00
|
2015-12-04 11:33:50+00:00
|
I'm geting the message when i open Visual Studio Code:
" Cannot validate the php file. The php program was not found. Use the 'php.validate.executablePath' setting to configure the location of 'php' "
|
completed
|
Cannot validate the php file. The php program was not found. I'm geting the message when i open Visual Studio Code:
" Cannot validate the php file. The php program was not found. Use the 'php.validate.executablePath' setting to configure the location of 'php' "
| 76 |
[] |
0
|
False
|
|
969
|
A string field that doesn't fit in the hover box messes up syntax highlighting
|
2015-12-03 15:05:21+00:00
|
2015-12-22 23:35:05+00:00
|
If during debugging you hover over an object whose representation does not fit in the hover box, it will cut it off and apply highlighting based on that. This causes an issue when you have a string: it will cut off the trailing quotes and mess up highlighting for subsequent fields.
|
completed
|
A string field that doesn't fit in the hover box messes up syntax highlighting If during debugging you hover over an object whose representation does not fit in the hover box, it will cut it off and apply highlighting based on that. This causes an issue when you have a string: it will cut off the trailing quotes and mess up highlighting for subsequent fields.
| 140 |
[] |
0
|
False
|
|
965
|
"Visual Studio Code has crashed" when editing an ES6 file
|
2015-12-03 13:49:47+00:00
|
2016-03-11 14:58:55+00:00
|
VSCode crashes every time I open an ES6 file, after a few seconds. This started happening after the 0.10.3 update.
Here's the output:
```
$ ./code --verbose
### VSCode main.js ###
c:\Program Files (x86)\Microsoft VS Code\resources\app { pathArguments: [],
programStart: 0,
workers: -1,
enablePerformance: false,
verboseLogging: true,
debugPluginHostPort: undefined,
debugBrkPluginHost: undefined,
logPluginHostCommunication: false,
firstrun: false,
openNewWindow: false,
openInSameWindow: false,
gotoLineMode: false,
pluginHomePath: undefined,
pluginDevelopmentPath: undefined,
pluginTestsPath: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
<--- Last few GCs --->
11777 ms: Scavenge 715.1 (742.6) -> 715.1 (742.6) MB, 0.2 / 0 ms (+ 5.0 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
11865 ms: Mark-sweep 715.1 (742.6) -> 714.3 (738.6) MB, 88.2 / 1 ms (+ 6.0 ms in 2 steps since start of marking, biggest step 5.0 ms) [last resort gc].
11919 ms: Mark-sweep 714.3 (738.6) -> 714.4 (737.6) MB, 54.1 / 1 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 12320E39 <String[7]: file://>
1: slowToString [buffer.js:344] [pc=0F1B78F8] (this=0F9F3DA5 <an Uint8Array with map 34609681>,encoding=123236C9 <String[4]: utf8>,start=0,end=3694146)
2: toString [buffer.js:~371] [pc=24AAD709] (this=0F9F3DA5 <an Uint8Array with map 34609681>)
3: arguments adaptor frame: 3->0
4: write [string_decoder.js:129] [pc=24A3D6FD] (this=0F9FD0C5 <an InternalDecoder with map 2C6981DD>...
[VS Code]: render process crashed!
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle
```
|
completed
|
"Visual Studio Code has crashed" when editing an ES6 file VSCode crashes every time I open an ES6 file, after a few seconds. This started happening after the 0.10.3 update.
Here's the output:
```
$ ./code --verbose
### VSCode main.js ###
c:\Program Files (x86)\Microsoft VS Code\resources\app { pathArguments: [],
programStart: 0,
workers: -1,
enablePerformance: false,
verboseLogging: true,
debugPluginHostPort: undefined,
debugBrkPluginHost: undefined,
logPluginHostCommunication: false,
firstrun: false,
openNewWindow: false,
openInSameWindow: false,
gotoLineMode: false,
pluginHomePath: undefined,
pluginDevelopmentPath: undefined,
pluginTestsPath: undefined }
Lifecycle#unload() 1
IPC#vscode-workbenchLoaded
<--- Last few GCs --->
11777 ms: Scavenge 715.1 (742.6) -> 715.1 (742.6) MB, 0.2 / 0 ms (+ 5.0 ms in 1 steps since last GC) [allocation failure] [incremental marking delaying mark-sweep].
11865 ms: Mark-sweep 715.1 (742.6) -> 714.3 (738.6) MB, 88.2 / 1 ms (+ 6.0 ms in 2 steps since start of marking, biggest step 5.0 ms) [last resort gc].
11919 ms: Mark-sweep 714.3 (738.6) -> 714.4 (737.6) MB, 54.1 / 1 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 12320E39 <String[7]: file://>
1: slowToString [buffer.js:344] [pc=0F1B78F8] (this=0F9F3DA5 <an Uint8Array with map 34609681>,encoding=123236C9 <String[4]: utf8>,start=0,end=3694146)
2: toString [buffer.js:~371] [pc=24AAD709] (this=0F9F3DA5 <an Uint8Array with map 34609681>)
3: arguments adaptor frame: 3->0
4: write [string_decoder.js:129] [pc=24A3D6FD] (this=0F9FD0C5 <an InternalDecoder with map 2C6981DD>...
[VS Code]: render process crashed!
Lifecycle#window-all-closed
Lifecycle#before-quit
App#dispose: deleting running instance handle
```
| 643 |
[] |
0
|
False
|
|
964
|
Cmd+P broken
|
2015-12-03 13:49:07+00:00
|
2015-12-03 14:53:53+00:00
|
It only search recent, not on disk
|
completed
|
Cmd+P broken It only search recent, not on disk
| 16 |
[] |
0
|
False
|
|
960
|
extensionHost debugging: reattach does not connect to debugServer
|
2015-12-03 11:17:34+00:00
|
2015-12-03 14:40:55+00:00
|
If I have configured 'debugServer' in my launch config, the initial launch connects correctly to the debugServer, but reloading the extensionHost (which results in a 'reattach' in VSCode) does not connect to the debugServer but starts a normal debugServer instead.
|
completed
|
extensionHost debugging: reattach does not connect to debugServer If I have configured 'debugServer' in my launch config, the initial launch connects correctly to the debugServer, but reloading the extensionHost (which results in a 'reattach' in VSCode) does not connect to the debugServer but starts a normal debugServer instead.
| 89 |
[] |
0
|
False
|
|
959
|
Fonts become fuzzy after zooming and scrolling
|
2015-12-03 10:30:25+00:00
|
2016-05-06 15:09:21+00:00
|
- Zoom once using Ctrl-+.
- Click on a file to open it. Text in editor looks crisp.
- Scroll down in editor and the font of the text goes fuzzy.
|
completed
|
Fonts become fuzzy after zooming and scrolling - Zoom once using Ctrl-+.
- Click on a file to open it. Text in editor looks crisp.
- Scroll down in editor and the font of the text goes fuzzy.
| 53 |
[] |
0
|
False
|
|
952
|
TypeError: Cannot read property '_acceptIsDirty' of undefined
|
2015-12-03 06:59:19+00:00
|
2015-12-03 08:42:26+00:00
|
Seeing this in latest, making the PH go crazy:
|
completed
|
TypeError: Cannot read property '_acceptIsDirty' of undefined Seeing this in latest, making the PH go crazy:
| 84 |
[] |
0
|
False
|
|
949
|
Remove name "Visual Studio" from vscode.d.ts
|
2015-12-03 00:54:44+00:00
|
2015-12-03 08:58:33+00:00
|
There is a comment on line 13 in [`src/vs/vscode.d.ts`](https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts) that refers to "Visual Studio Code". We should not use "Visual Studio" in the sources as the name is a customization done during the build (from [`product.json`](https://github.com/Microsoft/vscode/blob/master/product.json)). Suggest just using the term `Code`.
|
completed
|
Remove name "Visual Studio" from vscode.d.ts There is a comment on line 13 in [`src/vs/vscode.d.ts`](https://github.com/Microsoft/vscode/blob/master/src/vs/vscode.d.ts) that refers to "Visual Studio Code". We should not use "Visual Studio" in the sources as the name is a customization done during the build (from [`product.json`](https://github.com/Microsoft/vscode/blob/master/product.json)). Suggest just using the term `Code`.
| 148 |
[] |
0
|
False
|
|
946
|
Creating new file with no file extension
|
2015-12-03 00:03:55+00:00
|
2015-12-03 12:44:31+00:00
|
Try to create a new file, name it "README", and set the type as "_._ all files". It will say the filename is invalid. Surrounding README in quotation marks is a workaround.
|
completed
|
Creating new file with no file extension Try to create a new file, name it "README", and set the type as "_._ all files". It will say the filename is invalid. Surrounding README in quotation marks is a workaround.
| 62 |
[] |
0
|
False
|
|
942
|
[lua] "goto" missing in Lua syntax highlighting
|
2015-12-02 22:02:23+00:00
|
2015-12-03 12:47:31+00:00
|
When using the goto keyword, it is not highlighted, nor is the label selected.
Example:
```
function func()
if this == that then
do = this
goto continueHere
elseif this2 == that2 then
::continueHere::
end
end
```
Ignoring the terrible example itself, the problem occurs on line 4 where no highlighting will occur. Line 6, where the label is, highlights correctly, however.
|
completed
|
[lua] "goto" missing in Lua syntax highlighting When using the goto keyword, it is not highlighted, nor is the label selected.
Example:
```
function func()
if this == that then
do = this
goto continueHere
elseif this2 == that2 then
::continueHere::
end
end
```
Ignoring the terrible example itself, the problem occurs on line 4 where no highlighting will occur. Line 6, where the label is, highlights correctly, however.
| 119 |
[] |
0
|
False
|
|
933
|
Comparing a number variable to a string shows a warning even though assigning a string is perfectly fine
|
2015-12-02 16:12:59+00:00
|
2016-03-14 08:48:13+00:00
|
Consider the following example:
```
function myFunc(myString) {
let myVar = Infinity;
myVar = myString.substring(1);
if(myVar == 'ello') {
}
}
```
This will show a warning at the `if` statement saying the `==` operator can't be used to compare a string and a number. Aside from the discussion whether this should be done in the first place, I think we can agree that it's handled inconsistently here: if we can assign a string to a number just fine then comparing a string to a number should be okay as well (and certainly if we use `==` instead of `===`).
|
completed
|
Comparing a number variable to a string shows a warning even though assigning a string is perfectly fine Consider the following example:
```
function myFunc(myString) {
let myVar = Infinity;
myVar = myString.substring(1);
if(myVar == 'ello') {
}
}
```
This will show a warning at the `if` statement saying the `==` operator can't be used to compare a string and a number. Aside from the discussion whether this should be done in the first place, I think we can agree that it's handled inconsistently here: if we can assign a string to a number just fine then comparing a string to a number should be okay as well (and certainly if we use `==` instead of `===`).
| 178 |
[] |
0
|
False
|
|
931
|
Windows: Cannot save hidden files
|
2015-12-02 15:48:17+00:00
|
2017-08-15 06:40:29+00:00
|
node.js returns a EPERM error when trying to save files with hidden attribute.
|
completed
|
Windows: Cannot save hidden files node.js returns a EPERM error when trying to save files with hidden attribute.
| 31 |
[] |
0
|
False
|
|
929
|
Windows 10: focus is not put to window but taskbar blinks
|
2015-12-02 14:46:33+00:00
|
2016-10-07 10:11:38+00:00
|
This can happen when code is already running and you start it again from the command line: The process that is started is killed very early after sending a IPC message to the running instance and that running instance is then trying to restore/focus the last active window which often fails.
Related: https://github.com/atom/electron/issues/2867
As a **workaround** if you have access to the windows registry:
- regedit.exe
- find `ForegroundLockTimeout`
- change its value to `10` (decimal)
- restart windows
|
completed
|
Windows 10: focus is not put to window but taskbar blinks This can happen when code is already running and you start it again from the command line: The process that is started is killed very early after sending a IPC message to the running instance and that running instance is then trying to restore/focus the last active window which often fails.
Related: https://github.com/atom/electron/issues/2867
As a **workaround** if you have access to the windows registry:
- regedit.exe
- find `ForegroundLockTimeout`
- change its value to `10` (decimal)
- restart windows
| 143 |
[] |
0
|
False
|
|
928
|
[html] punctuation for tags can not be colored by syntax themes
|
2015-12-02 14:44:00+00:00
|
2015-12-03 08:52:08+00:00
|
I have tried several themes from the marketplace and created a few of my own. Punctuation on HTML files, such as `< > </> =` cannot be colored by the theme. When using a dark theme, for example, I always get the original default medium/light blue.
|
completed
|
[html] punctuation for tags can not be colored by syntax themes I have tried several themes from the marketplace and created a few of my own. Punctuation on HTML files, such as `< > </> =` cannot be colored by the theme. When using a dark theme, for example, I always get the original default medium/light blue.
| 140 |
[] |
0
|
False
|
|
927
|
File/Text search cancellation fails
|
2015-12-02 14:40:02+00:00
|
2015-12-03 14:54:04+00:00
|
We should introduce real cancellation tokens for the search API instead of relying on the promise cancel which can easily get lost with all the chaining.
- [x] fix throttled-delayer use to cancel a search when typing and revisit 100ms delay
- [x] consider adopting a maxResults for quick open too
|
completed
|
File/Text search cancellation fails We should introduce real cancellation tokens for the search API instead of relying on the promise cancel which can easily get lost with all the chaining.
- [x] fix throttled-delayer use to cancel a search when typing and revisit 100ms delay
- [x] consider adopting a maxResults for quick open too
| 85 |
[] |
0
|
False
|
|
926
|
Can't save .htaccess file. EPERM error.
|
2015-12-02 14:13:05+00:00
|
2015-12-02 15:23:35+00:00
|
Even running vscode as administrator gives me the same error.
|
completed
|
Can't save .htaccess file. EPERM error. 
Even running vscode as administrator gives me the same error.
| 83 |
[] |
0
|
False
|
|
911
|
Task progress does not stop turning
|
2015-12-02 11:00:40+00:00
|
2015-12-02 14:53:26+00:00
|
- git clone https://github.com/Microsoft/vscode-extension-samples.git
- cd to the new folder
- `npm run install-all`
- `code .`
- in the debug viewlet, run 'Launch decorator sample'
- note that the task progress is rotating
- terminate the debug connection
- task progress is still turning
|
completed
|
Task progress does not stop turning - git clone https://github.com/Microsoft/vscode-extension-samples.git
- cd to the new folder
- `npm run install-all`
- `code .`
- in the debug viewlet, run 'Launch decorator sample'
- note that the task progress is rotating
- terminate the debug connection
- task progress is still turning
| 93 |
[] |
0
|
False
|
|
909
|
Errors remain even when fixed when running in watch mode
|
2015-12-02 09:54:29+00:00
|
2015-12-08 09:48:33+00:00
|
I run webpack from Visual Studio Code (0.10.3). When an error is found by webpack it is found by Visual Studio Code (I can see it when I press Ctrl+Shift+M).
But when I correct the error I can still see it when I press Ctrl+Shift+M. I would like to dissapear from that list so I know which real errors that real.
Even when I terminate the task and run it again the error remain when I press Ctrl+Shift+M.
When I trigger the task normally (Ctrl+Shift+B) without watch then the errors dissapear after I fix them.
This is the task from tasks.json
```
"args": [
"-d",
"--watch"
],
"suppressTaskName": true,
"taskName": "webpack watch",
"showOutput": "silent",
"isWatching": true,
"problemMatcher": [{
"owner": "webpack",
"fileLocation": ["relative", "${workspaceRoot}"],
"severity": "warning",
"pattern": [
{
"regexp": "WARNING in (.*)",
"file" : 1
},
{
"regexp": "\\[(\\d+),\\s(\\d+)\\]:\\s(.*)",
"line":1,
"column": 2,
"message": 3
}
]
},
{
"owner": "webpack",
"fileLocation": ["relative", "${workspaceRoot}"],
"severity": "error",
"pattern": [
{
"regexp": "ERROR in (.*)",
"file" : 1
},
{
"regexp": "\\((\\d+),(\\d+)\\):(.*)",
"line":1,
"column": 2,
"message": 3
}
]
}]
```
|
completed
|
Errors remain even when fixed when running in watch mode I run webpack from Visual Studio Code (0.10.3). When an error is found by webpack it is found by Visual Studio Code (I can see it when I press Ctrl+Shift+M).
But when I correct the error I can still see it when I press Ctrl+Shift+M. I would like to dissapear from that list so I know which real errors that real.
Even when I terminate the task and run it again the error remain when I press Ctrl+Shift+M.
When I trigger the task normally (Ctrl+Shift+B) without watch then the errors dissapear after I fix them.
This is the task from tasks.json
```
"args": [
"-d",
"--watch"
],
"suppressTaskName": true,
"taskName": "webpack watch",
"showOutput": "silent",
"isWatching": true,
"problemMatcher": [{
"owner": "webpack",
"fileLocation": ["relative", "${workspaceRoot}"],
"severity": "warning",
"pattern": [
{
"regexp": "WARNING in (.*)",
"file" : 1
},
{
"regexp": "\\[(\\d+),\\s(\\d+)\\]:\\s(.*)",
"line":1,
"column": 2,
"message": 3
}
]
},
{
"owner": "webpack",
"fileLocation": ["relative", "${workspaceRoot}"],
"severity": "error",
"pattern": [
{
"regexp": "ERROR in (.*)",
"file" : 1
},
{
"regexp": "\\((\\d+),(\\d+)\\):(.*)",
"line":1,
"column": 2,
"message": 3
}
]
}]
```
| 467 |
[] |
0
|
False
|
|
904
|
Massive issue on Mac OSX with emoji
|
2015-12-02 09:12:12+00:00
|
2016-01-26 15:44:01+00:00
|
I don't know what's going on, but when you insert an emoji, there is some odd repetition of markup happening.
|
completed
|
Massive issue on Mac OSX with emoji I don't know what's going on, but when you insert an emoji, there is some odd repetition of markup happening.
| 95 |
[] |
0
|
False
|
|
901
|
Bug: Code + Git = deleted files
|
2015-12-02 08:48:59+00:00
|
2016-07-11 10:30:16+00:00
|
Several times now I've had mysteriously deleted files when doing a git pull in a console while Visual Studio Code is running. I've seen this roughly since version 0.10.
It seems that when auto-merging, Git is able to delete a file but not able to write the merged file back if it's open in Code. However that is just a hypothesis.
Seen the issue last with git version 1.9.5.msysgit.1 and Code 0.10.2.
|
completed
|
Bug: Code + Git = deleted files Several times now I've had mysteriously deleted files when doing a git pull in a console while Visual Studio Code is running. I've seen this roughly since version 0.10.
It seems that when auto-merging, Git is able to delete a file but not able to write the merged file back if it's open in Code. However that is just a hypothesis.
Seen the issue last with git version 1.9.5.msysgit.1 and Code 0.10.2.
| 117 |
[] |
0
|
False
|
|
899
|
Using shebangs in TypeScript are generating errors.
|
2015-12-02 04:57:04+00:00
|
2016-03-02 06:09:18+00:00
|
I'm working on a Node script using TypeScript and the editor is generating this annoying erros.
TS compiler is working fine, it compiles my script without problems :)
Here's a screenshot of the error.
Shebang is present at the top of the file:
# ! /usr/bin/env node
|
completed
|
Using shebangs in TypeScript are generating errors. I'm working on a Node script using TypeScript and the editor is generating this annoying erros.
TS compiler is working fine, it compiles my script without problems :)
Here's a screenshot of the error.
Shebang is present at the top of the file:
# ! /usr/bin/env node
| 141 |
[] |
0
|
False
|
|
896
|
Input sources panel's position is wrong when begin to type
|
2015-12-02 02:14:21+00:00
|
2016-07-04 16:01:05+00:00
|
I use **Pinyin - Simplified** to input Chinese character .
<img width="718" alt="Pinyin - Simplified Input Source" src="https://cloud.githubusercontent.com/assets/344283/11520152/a4c67190-98db-11e5-99ec-d1ed8b85226f.png">
When I begin typing, the input sources panel positioned unexpectedly.
It should perform like Sublime Text.
|
completed
|
Input sources panel's position is wrong when begin to type I use **Pinyin - Simplified** to input Chinese character .
<img width="718" alt="Pinyin - Simplified Input Source" src="https://cloud.githubusercontent.com/assets/344283/11520152/a4c67190-98db-11e5-99ec-d1ed8b85226f.png">
When I begin typing, the input sources panel positioned unexpectedly.
It should perform like Sublime Text.
| 241 |
[] |
0
|
False
|
|
881
|
[json] VS Code suggests another property when a property's casing is not correct.
|
2015-12-01 19:14:40+00:00
|
2015-12-03 20:58:32+00:00
|
The error in following JSON against schema is: "resources\properties\osProfile\computername" should be "computerName".
But VS Code shows two errors here:
1. on "Microsoft.Compute/virtualMachines", error message is: Value is not an accepted Value. Valid values: ["Microsoft.Network/publicIPAddresses"]
2. on “properties", error message is: Missing property "publicIpAllocationMethod"
It would be good if the error can be on the "computename" or at lease on "osProfile" about missing required property "computerName", ("computerName" is a required property according to schema)
JSON example:
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"resources": [
{
"apiVersion": "2015-06-15",
"type": "Microsoft.Compute/virtualMachines",
"name": "a",
"location": "West US",
"properties": {
"hardwareProfile": {
"vmSize": "Small"
},
"osProfile": {
"computername": "a",
"adminUsername": "a",
"adminPassword": "a"
},
"storageProfile": {
"imageReference": {
"publisher": "a",
"offer": "a",
"sku": "a",
"version": "latest"
},
"osDisk": {
"name": "osdisk",
"vhd": {
"uri": "[concat('http://', 'b','.blob.core.windows.net/',variables('vmStorageAccountContainerName'),'/',variables('OSDiskName'),'.vhd')]"
},
"caching": "ReadWrite",
"createOption": "FromImage"
}
},
"networkProfile": {
"networkInterfaces": [
{
"id": "[resourceId('Microsoft.Network/networkInterfaces',variables('nicName'))]"
}
]
},
"diagnosticsProfile": {
"bootDiagnostics": {
"enabled": "true",
"storageUri": "[concat('http://',parameters('newStorageAccountName'),'.blob.core.windows.net')]"
}
}
}
}
]
}
|
completed
|
[json] VS Code suggests another property when a property's casing is not correct. The error in following JSON against schema is: "resources\properties\osProfile\computername" should be "computerName".
But VS Code shows two errors here:
1. on "Microsoft.Compute/virtualMachines", error message is: Value is not an accepted Value. Valid values: ["Microsoft.Network/publicIPAddresses"]
2. on “properties", error message is: Missing property "publicIpAllocationMethod"
It would be good if the error can be on the "computename" or at lease on "osProfile" about missing required property "computerName", ("computerName" is a required property according to schema)
JSON example:
{
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"resources": [
{
"apiVersion": "2015-06-15",
"type": "Microsoft.Compute/virtualMachines",
"name": "a",
"location": "West US",
"properties": {
"hardwareProfile": {
"vmSize": "Small"
},
"osProfile": {
"computername": "a",
"adminUsername": "a",
"adminPassword": "a"
},
"storageProfile": {
"imageReference": {
"publisher": "a",
"offer": "a",
"sku": "a",
"version": "latest"
},
"osDisk": {
"name": "osdisk",
"vhd": {
"uri": "[concat('http://', 'b','.blob.core.windows.net/',variables('vmStorageAccountContainerName'),'/',variables('OSDiskName'),'.vhd')]"
},
"caching": "ReadWrite",
"createOption": "FromImage"
}
},
"networkProfile": {
"networkInterfaces": [
{
"id": "[resourceId('Microsoft.Network/networkInterfaces',variables('nicName'))]"
}
]
},
"diagnosticsProfile": {
"bootDiagnostics": {
"enabled": "true",
"storageUri": "[concat('http://',parameters('newStorageAccountName'),'.blob.core.windows.net')]"
}
}
}
}
]
}
| 639 |
[] |
0
|
False
|
|
878
|
DocumentFilter does not work for dockerfiles
|
2015-12-01 17:37:06+00:00
|
2016-01-07 11:06:54+00:00
|
We want our docker extension to support yml and docker files when they are named like ‘docker-compose-dev.yml’ or ‘dockerfile-dev’ etc. Using the DocumentFilter pattern `**/docker-compose*.yml` I was able to get this to work, however DocumentFilter `**/dockerfile*` does not work – I don’t even get syntax coloring.
|
completed
|
DocumentFilter does not work for dockerfiles We want our docker extension to support yml and docker files when they are named like ‘docker-compose-dev.yml’ or ‘dockerfile-dev’ etc. Using the DocumentFilter pattern `**/docker-compose*.yml` I was able to get this to work, however DocumentFilter `**/dockerfile*` does not work – I don’t even get syntax coloring.
| 114 |
[] |
0
|
False
|
|
872
|
Improve error message when no command is bound to a command contribution
|
2015-12-01 16:06:41+00:00
|
2015-12-15 14:10:57+00:00
|
When a command is defined in the package.json but no Command is registered for it then the error message should provide more guidance for how to fix the problem.
see #810
|
completed
|
Improve error message when no command is bound to a command contribution When a command is defined in the package.json but no Command is registered for it then the error message should provide more guidance for how to fix the problem.
see #810
| 55 |
[] |
0
|
False
|
|
864
|
Report unverified breakpoints back to user
|
2015-12-01 14:36:48+00:00
|
2015-12-02 10:47:54+00:00
|
If a user sets a breakpoint in a typescript file and no source map exists, the breakpoint jumps to a strange place but still looks good.
What should happen:
The breakpoint should not move because the backend cannot map the breakpoint to javascript. But instead the breakpoint should indicate that it could not be verified (and will never fire).
This is the associated issue in node-debug: Microsoft/vscode-node-debug#13
|
completed
|
Report unverified breakpoints back to user If a user sets a breakpoint in a typescript file and no source map exists, the breakpoint jumps to a strange place but still looks good.
What should happen:
The breakpoint should not move because the backend cannot map the breakpoint to javascript. But instead the breakpoint should indicate that it could not be verified (and will never fire).
This is the associated issue in node-debug: Microsoft/vscode-node-debug#13
| 113 |
[] |
0
|
False
|
|
862
|
Unable to start Code on Ubuntu
|
2015-12-01 13:40:42+00:00
|
2016-01-04 13:18:16+00:00
|
I am running Ubuntu 15.04, without a GUI. My home directory is an NFS share mounted via automount, my account is via NIS.
After installing Gnome I have been able to get the Code executable to run by double clicking on the program from a file explorer. But not from a shell, either on the console or a remote ssh.
If I run the Code program from my normal ssh login it runs waits a while and then exits, with no error message or anything.
If I run it with the sudo Code command it runs up and works fine, apart from the whole running as root issue :(.
I suspect it's a file permission thing but am unable to track down what it could be.
Regards
John
|
completed
|
Unable to start Code on Ubuntu I am running Ubuntu 15.04, without a GUI. My home directory is an NFS share mounted via automount, my account is via NIS.
After installing Gnome I have been able to get the Code executable to run by double clicking on the program from a file explorer. But not from a shell, either on the console or a remote ssh.
If I run the Code program from my normal ssh login it runs waits a while and then exits, with no error message or anything.
If I run it with the sudo Code command it runs up and works fine, apart from the whole running as root issue :(.
I suspect it's a file permission thing but am unable to track down what it could be.
Regards
John
| 172 |
[] |
0
|
False
|
|
855
|
do not try to reconnect on real quit
|
2015-12-01 11:00:47+00:00
|
2015-12-04 10:16:23+00:00
|
I think we should start to look into a solution to this because we are now adding workarounds for this issue when running unit tests: The issue is that when the unit test is done, I quit the PH with process.exit(). This nicely closes the window but the debugger wants to reconnect right after and fails (not with an error message, but its weird to see the debug viewlet progress spinning for 2 seconds).
We also see this when you Cmd+Q the extension host to terminate the session.
I am open to ideas what to do here, somehow the PH needs to signal back how it was terminated.
|
completed
|
do not try to reconnect on real quit I think we should start to look into a solution to this because we are now adding workarounds for this issue when running unit tests: The issue is that when the unit test is done, I quit the PH with process.exit(). This nicely closes the window but the debugger wants to reconnect right after and fails (not with an error message, but its weird to see the debug viewlet progress spinning for 2 seconds).
We also see this when you Cmd+Q the extension host to terminate the session.
I am open to ideas what to do here, somehow the PH needs to signal back how it was terminated.
| 152 |
[] |
0
|
False
|
|
850
|
'install extension' should be more clear which extensions are already installed
|
2015-12-01 09:59:18+00:00
|
2016-07-05 16:08:59+00:00
|
- I already have the HTMLHint extension already installed
- press F1 and type 'ext install html'
- I would expect to only see extensions that I can install. But also HtmlHint shows up. Pressing enter on it has no effect. There's a x button that shows it can be uninstalled, but I think this is not clear enough which of the entries can be installed and which not.
Either make this it visually more prominent, or why not hiding already installed extensions? For looking at the installed extensions I can use 'show installed extensions'.
|
completed
|
'install extension' should be more clear which extensions are already installed - I already have the HTMLHint extension already installed
- press F1 and type 'ext install html'
- I would expect to only see extensions that I can install. But also HtmlHint shows up. Pressing enter on it has no effect. There's a x button that shows it can be uninstalled, but I think this is not clear enough which of the entries can be installed and which not.
Either make this it visually more prominent, or why not hiding already installed extensions? For looking at the installed extensions I can use 'show installed extensions'.
| 152 |
[] |
0
|
False
|
|
843
|
Error message text cannot be multiline
|
2015-12-01 03:59:57+00:00
|
2016-04-07 11:12:08+00:00
|
https://github.com/Microsoft/vscode-go/issues/132 appears to be unfixable with the current Code API, which doesn't render newline characters in the message as newlines in the UI, and doesn't allow any formatting construct to provide multiple lines of content (as the Hover type does).
For some compilers, multiline error messages which take advantage of both newlines and tabs to provide helpful formatted error reports are fairly common, and cannot be rendered well in Code.
|
completed
|
Error message text cannot be multiline https://github.com/Microsoft/vscode-go/issues/132 appears to be unfixable with the current Code API, which doesn't render newline characters in the message as newlines in the UI, and doesn't allow any formatting construct to provide multiple lines of content (as the Hover type does).
For some compilers, multiline error messages which take advantage of both newlines and tabs to provide helpful formatted error reports are fairly common, and cannot be rendered well in Code.
| 121 |
[] |
0
|
False
|
|
842
|
Long line of hover text gets cut off instead of line wrapping
|
2015-12-01 03:49:37+00:00
|
2015-12-10 09:00:33+00:00
|
https://github.com/Microsoft/vscode-go/issues/131 appears to be unfixable with the current API, since lines aren't being automatically wrapped, there is no way to request them to be wrapped, and there is no apriori known length at which to proactively wrap that will look good in general.
|
completed
|
Long line of hover text gets cut off instead of line wrapping https://github.com/Microsoft/vscode-go/issues/131 appears to be unfixable with the current API, since lines aren't being automatically wrapped, there is no way to request them to be wrapped, and there is no apriori known length at which to proactively wrap that will look good in general.
| 90 |
[] |
0
|
False
|
|
841
|
Annoying bar
|
2015-12-01 01:25:36+00:00
|
2015-12-01 16:58:28+00:00
|
Although this is somewhat small, this really gets me; whenever I create a new file (that is the key here, this doesn't happen with ones previously created and opened using the "open with code" context menu) after passing line 25 there is a bar that is a different color overlayed on the line numbers, which as far as I can tell extends infinitely.
|
completed
|
Annoying bar Although this is somewhat small, this really gets me; whenever I create a new file (that is the key here, this doesn't happen with ones previously created and opened using the "open with code" context menu) after passing line 25 there is a bar that is a different color overlayed on the line numbers, which as far as I can tell extends infinitely.
| 85 |
[] |
0
|
False
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.