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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
1861
|
ugly working files section
|
2016-01-08 08:11:38+00:00
|
2016-01-08 09:13:52+00:00
|
I guess this is due to the size changes. The unsaved-banner looks bad in many ways
|
completed
|
ugly working files section I guess this is due to the size changes. The unsaved-banner looks bad in many ways
| 88 |
[] |
0
|
False
|
|
1859
|
prevent bogus hovers
|
2016-01-07 21:36:23+00:00
|
2016-01-08 15:28:26+00:00
|
I was in a debugging session and opened a completely unrelated file in VS Code.
When moving the mouse over a "this" a hover appeared and seemed to show the attributes of the this.
But this file was not in scope (that is not shown in the stack), so it makes no sense to show any hovers.
I understand that without scope information it is difficult to show correct hovers but I suggest that we try to prevent showing hovers for files that are not in scope at all.
|
completed
|
prevent bogus hovers I was in a debugging session and opened a completely unrelated file in VS Code.
When moving the mouse over a "this" a hover appeared and seemed to show the attributes of the this.
But this file was not in scope (that is not shown in the stack), so it makes no sense to show any hovers.
I understand that without scope information it is difficult to show correct hovers but I suggest that we try to prevent showing hovers for files that are not in scope at all.
| 177 |
[] |
0
|
False
|
|
1857
|
F3, Find Next, acts like "Find Under Cursor"
|
2016-01-07 17:15:42+00:00
|
2016-01-10 11:09:45+00:00
|
tl; dr: F3 acts like Ctrl+F3 in Visual Studio
##### More details:
Let's say the text editor contains the following 4 lines:
```
ABC
ABC
XYZ
ABC
```
The cursor is at the very top, of the file, at the first ABC. I hit Ctrl+F to show the Find dialog. I type ABC. The first ABC is highlighted. I hit Esc to exit the Find dialog.
The cursor is now at end of the first line, with ABC on that line highlighted. I hit delete to remove it and change the text to XYZ. At this point the text editor looks like this:
```
XYZ
ABC
XYZ
ABC
```
The cursor is at end of the first line.
I hit F3 to "Find Next" to find the next occurrence of ABC, but instead it searches for XYZ. The reason is because hitting F3 changes what's being searched for. In other words, F3 acts like Ctrl+F3 in Visual Studio
##### Version I'm running:
[Window Title]
Visual Studio Code
[Main Instruction]
Visual Studio Code
[Content]
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:34:58.895Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
[OK]
|
completed
|
F3, Find Next, acts like "Find Under Cursor" tl; dr: F3 acts like Ctrl+F3 in Visual Studio
##### More details:
Let's say the text editor contains the following 4 lines:
```
ABC
ABC
XYZ
ABC
```
The cursor is at the very top, of the file, at the first ABC. I hit Ctrl+F to show the Find dialog. I type ABC. The first ABC is highlighted. I hit Esc to exit the Find dialog.
The cursor is now at end of the first line, with ABC on that line highlighted. I hit delete to remove it and change the text to XYZ. At this point the text editor looks like this:
```
XYZ
ABC
XYZ
ABC
```
The cursor is at end of the first line.
I hit F3 to "Find Next" to find the next occurrence of ABC, but instead it searches for XYZ. The reason is because hitting F3 changes what's being searched for. In other words, F3 acts like Ctrl+F3 in Visual Studio
##### Version I'm running:
[Window Title]
Visual Studio Code
[Main Instruction]
Visual Studio Code
[Content]
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:34:58.895Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
[OK]
| 330 |
[] |
0
|
False
|
|
1855
|
Extremely slow loading and operation
|
2016-01-07 15:23:24+00:00
|
2016-01-14 14:24:14+00:00
|
Initial loading of VS Code can take between 10 and 20 seconds.
The `Reload Window` command takes about 10 seconds to complete.
I've tried it from the installer and also building from source with similar problems.
CPU profiling shows `ChildProcess.spawn` is the biggest problem, which calls all the way down to `node.js _tickCallback`. I'd be happy to email someone the profile if it would help.
I suppose this issue could be with node itself? I'm at a loss, since VS Code works perfectly on my home computers which have no proxy.
**System Properties**
- Windows 7 Enterprise SP1
- Intel i5-4590, 8GB RAM, Samsung 950Pro SSD
**Corporate Environment**
- Behind a NTLM proxy. Have CNTLM installed with environment variables `http_proxy` and `https_proxy` pointing to it. npm works fine with this setup.
- Symantec Endpoint is installed also.
|
completed
|
Extremely slow loading and operation Initial loading of VS Code can take between 10 and 20 seconds.
The `Reload Window` command takes about 10 seconds to complete.
I've tried it from the installer and also building from source with similar problems.
CPU profiling shows `ChildProcess.spawn` is the biggest problem, which calls all the way down to `node.js _tickCallback`. I'd be happy to email someone the profile if it would help.
I suppose this issue could be with node itself? I'm at a loss, since VS Code works perfectly on my home computers which have no proxy.
**System Properties**
- Windows 7 Enterprise SP1
- Intel i5-4590, 8GB RAM, Samsung 950Pro SSD
**Corporate Environment**
- Behind a NTLM proxy. Have CNTLM installed with environment variables `http_proxy` and `https_proxy` pointing to it. npm works fine with this setup.
- Symantec Endpoint is installed also.
| 235 |
[] |
0
|
False
|
|
1850
|
Text highlighted with double click intermittently can't be edited
|
2016-01-07 10:29:10+00:00
|
2016-03-17 12:13:03+00:00
|
Hi
Before I continue I just want to say thanks for all the hard work on making visual studio code a fantastic editor. I prefer it to WebStorm, Atom, Sublime and anything else!
Ok to the main point, I have noticed what I think is a bug.
When editing simple JS files (although not tried with other languages), if I double click a word (to highlight it) and then start tying (i.e. to replace it), it sometimes ignores my typing.
I'm using the standard dark theme and I have noticed that when this is the case, the highlight is a slightly different colour to the normal editable selected text highlight.
I have also noticed that is happens more often if I double click quickly on a word, as opposed to if I double click more slowly.
I have a feeling that because this is running on Electron and essentially some kind of web application, maybe there is a race condition of sorts where if I double click too fast, the electron framework detects a select "span element" as opposed to the editor detecting that I'm highlighting a word for editing.
It might be a bug in the underlying Electron framework and not VS Code itself, but I have no idea, just suggesting. I have asked a friend who uses Atom on the same setup as me (also uses Electron) and he says he can't replicate, but he did say he uses a plugin which highlights the same words as the selected word (https://atom.io/packages/highlight-selected).
For additional information that might be of relevance in reproducing the issue, I am using VS Code 0.10.6 (latest release), Mac OS X (version 10.10.5), using the application in full screen mode (i.e. Command+Ctrl+F) and using an external USB mouse.
|
completed
|
Text highlighted with double click intermittently can't be edited Hi
Before I continue I just want to say thanks for all the hard work on making visual studio code a fantastic editor. I prefer it to WebStorm, Atom, Sublime and anything else!
Ok to the main point, I have noticed what I think is a bug.
When editing simple JS files (although not tried with other languages), if I double click a word (to highlight it) and then start tying (i.e. to replace it), it sometimes ignores my typing.
I'm using the standard dark theme and I have noticed that when this is the case, the highlight is a slightly different colour to the normal editable selected text highlight.
I have also noticed that is happens more often if I double click quickly on a word, as opposed to if I double click more slowly.
I have a feeling that because this is running on Electron and essentially some kind of web application, maybe there is a race condition of sorts where if I double click too fast, the electron framework detects a select "span element" as opposed to the editor detecting that I'm highlighting a word for editing.
It might be a bug in the underlying Electron framework and not VS Code itself, but I have no idea, just suggesting. I have asked a friend who uses Atom on the same setup as me (also uses Electron) and he says he can't replicate, but he did say he uses a plugin which highlights the same words as the selected word (https://atom.io/packages/highlight-selected).
For additional information that might be of relevance in reproducing the issue, I am using VS Code 0.10.6 (latest release), Mac OS X (version 10.10.5), using the application in full screen mode (i.e. Command+Ctrl+F) and using an external USB mouse.
| 421 |
[] |
0
|
False
|
|
1848
|
Sporadic test failures
|
2016-01-07 06:50:59+00:00
|
2016-01-07 11:38:18+00:00
|
```
1) ExtHostLanguageFeatures References, registration order:
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
at null.<anonymous> (C:\Users\appveyor\AppData\Roaming\npm\node_modules\mocha\lib\runnable.js:189:19)
```
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.873
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.870
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.868
|
completed
|
Sporadic test failures ```
1) ExtHostLanguageFeatures References, registration order:
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.
at null.<anonymous> (C:\Users\appveyor\AppData\Roaming\npm\node_modules\mocha\lib\runnable.js:189:19)
```
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.873
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.870
https://ci.appveyor.com/project/VSCode/vscode/build/1.0.868
| 173 |
[] |
0
|
False
|
|
1847
|
Cannot watch for file changes for files on disk root
|
2016-01-07 06:44:29+00:00
|
2016-09-19 09:32:41+00:00
|
Code version: 0.10.6
OS: Windows 10 x64
I have noticed that if a file is open in code and the file is changed externally, there is no way to know about it until I try to save it. I feel that if the file on the disk and file opened on code is in same state it should automatically reflect the changes made on the disk. This is what every modern text editor do.
Here is how to reproduce it.
- Create a text file.
- Open the file in Sublime text, Bracket and Code. In this situation the file is blank in all 3 editors.
- In Sublime text, write "Hello". Then save.
- Switch to Bracket, You will see "Hello".
- Switch to Code, you will see blank.
- Now again switch to Bracket, write "Hello world". Then save.
- Switch to Sublime text, You will see "Hello world".
- Switch to Code, you will see blank.
In both cases Code should reflect the changes made on disk.
|
completed
|
Cannot watch for file changes for files on disk root Code version: 0.10.6
OS: Windows 10 x64
I have noticed that if a file is open in code and the file is changed externally, there is no way to know about it until I try to save it. I feel that if the file on the disk and file opened on code is in same state it should automatically reflect the changes made on the disk. This is what every modern text editor do.
Here is how to reproduce it.
- Create a text file.
- Open the file in Sublime text, Bracket and Code. In this situation the file is blank in all 3 editors.
- In Sublime text, write "Hello". Then save.
- Switch to Bracket, You will see "Hello".
- Switch to Code, you will see blank.
- Now again switch to Bracket, write "Hello world". Then save.
- Switch to Sublime text, You will see "Hello world".
- Switch to Code, you will see blank.
In both cases Code should reflect the changes made on disk.
| 232 |
[] |
0
|
False
|
|
1846
|
Issue with markdown table
|
2016-01-07 05:58:08+00:00
|
2016-06-16 16:15:06+00:00
|
- VS Code version : 0.10.6
- OS system : windows 10 x64
Like this markdwon file :
```
key | value
--- | ---
\| | `|`
a \| b | `a | b`
```
VS Code preview :
github preview :
| key | value |
| --- | --- |
| | | `|` |
| a | b | `a | b` |
|
completed
|
Issue with markdown table - VS Code version : 0.10.6
- OS system : windows 10 x64
Like this markdwon file :
```
key | value
--- | ---
\| | `|`
a \| b | `a | b`
```
VS Code preview :
github preview :
| key | value |
| --- | --- |
| | | `|` |
| a | b | `a | b` |
| 176 |
[] |
0
|
False
|
|
1845
|
[php] Newline characters not escaped correctly
|
2016-01-07 05:34:04+00:00
|
2017-02-23 20:29:49+00:00
|
In many languages you can write a multi-line string by escaping the newline character, e.g.:
```
myString = "this \
is a multiline \
string";
```
However, in vscode, the text highlighting is broken when you have multi-line strings (the colour assigned to the string is only applied to the part of the string before the first back-slash, and as a result the text highlighting of the remaining part of the file is broken too).
I was able to reproduce the issue in PHP files, other languages might be affected too.
|
completed
|
[php] Newline characters not escaped correctly In many languages you can write a multi-line string by escaping the newline character, e.g.:
```
myString = "this \
is a multiline \
string";
```
However, in vscode, the text highlighting is broken when you have multi-line strings (the colour assigned to the string is only applied to the part of the string before the first back-slash, and as a result the text highlighting of the remaining part of the file is broken too).
I was able to reproduce the issue in PHP files, other languages might be affected too.
| 144 |
[] |
0
|
False
|
|
1840
|
mouse select doesn't work in rename text box on OS X
|
2016-01-06 23:57:20+00:00
|
2016-01-14 10:03:48+00:00
|
- select a (TypeScript) symbol for rename
- from context menu pick "Rename symbol"
- Observe: a text box appears
- trying to select the text in the text box with the mouse doesn't work
|
completed
|
mouse select doesn't work in rename text box on OS X - select a (TypeScript) symbol for rename
- from context menu pick "Rename symbol"
- Observe: a text box appears
- trying to select the text in the text box with the mouse doesn't work
| 63 |
[] |
0
|
False
|
|
1837
|
Italics break in Markdown mode when there's linebreak
|
2016-01-06 21:00:55+00:00
|
2018-02-09 22:53:30+00:00
|
Hello,
I noticed, that when editing Markdown text, italics is not shown correctly, if the text, that must be in italics, has linebreak. Same issue is also with bold. I attached screencapture below.
|
completed
|
Italics break in Markdown mode when there's linebreak Hello,
I noticed, that when editing Markdown text, italics is not shown correctly, if the text, that must be in italics, has linebreak. Same issue is also with bold. I attached screencapture below.
| 125 |
[] |
0
|
False
|
|
1825
|
Mouse Drag & Drop causes undocking of window
|
2016-01-06 11:02:53+00:00
|
2016-02-29 13:40:42+00:00
|
When drag a file (e.g. from explorer) to a docked Code window the file will be opened, but the window will be undocked. I have this issue on two seperate PC's.
Windows 7 ultimate 64bit
Code v 0.10.6
|
completed
|
Mouse Drag & Drop causes undocking of window When drag a file (e.g. from explorer) to a docked Code window the file will be opened, but the window will be undocked. I have this issue on two seperate PC's.
Windows 7 ultimate 64bit
Code v 0.10.6
| 70 |
[] |
0
|
False
|
|
1820
|
Putting a breakpoint in an internal module does not work
|
2016-01-06 09:38:58+00:00
|
2016-01-06 09:49:27+00:00
|
Start debugging, open an internal module (e.g module.js) and try to set a breakpoint in the internal module -> breakpoint validation removes breakpoint.
Debugging this showed that both arrays 'breakpoints' and 'lines' are empty.
|
completed
|
Putting a breakpoint in an internal module does not work Start debugging, open an internal module (e.g module.js) and try to set a breakpoint in the internal module -> breakpoint validation removes breakpoint.
Debugging this showed that both arrays 'breakpoints' and 'lines' are empty.
| 74 |
[] |
0
|
False
|
|
1798
|
"Undo Last Commit" should be grayed out if there are no commits.
|
2016-01-05 19:14:41+00:00
|
2017-11-23 13:26:34+00:00
|
After initializing git repository, but before committing, I can select "Undo Last Commit" from the "..." menu. That fails, of course. The resulting git reset HEAD~ won't work if there are no commits.
Undo Last Commit should be grayed out if HEAD doesn't have a parent.
Here's the log:
```
git init
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git reset HEAD~
fatal: ambiguous argument 'HEAD~': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
```
|
completed
|
"Undo Last Commit" should be grayed out if there are no commits. After initializing git repository, but before committing, I can select "Undo Last Commit" from the "..." menu. That fails, of course. The resulting git reset HEAD~ won't work if there are no commits.
Undo Last Commit should be grayed out if HEAD doesn't have a parent.
Here's the log:
```
git init
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git reset HEAD~
fatal: ambiguous argument 'HEAD~': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
git fetch
fatal: No remote repository specified. Please, specify either a URL or a
remote name from which new revisions should be fetched.
```
| 315 |
[] |
0
|
False
|
|
1796
|
HTTPS Authentication not working on Linux
|
2016-01-05 16:50:54+00:00
|
2016-04-07 13:53:20+00:00
|
On VS Code 0.10.6, when trying to sync changes in a HTTPS-backed Git repository, I get an error message which expands to [1] when I click 'show output', if VS Code was run from the desktop environment. If I close VS Code and run it from the terminal instead, I get the username and password prompts _on the terminal_ and typing from there just works (although it's obviously an uncomfortable task-switch).
[1]
```
git fetch
Missing ipc hook
error: unable to read askpass response from '$APPDIR/resources/app/out/vs/workbench/parts/git/electron-main/askpass.sh'
fatal: could not read Username for 'https://bitbucket.org': No such device or address
git pull
Missing ipc hook
error: unable to read askpass response from '$APPDIR/resources/app/out/vs/workbench/parts/git/electron-main/askpass.sh'
fatal: could not read Username for 'https://bitbucket.org': No such device or address
```
(Note: for conciseness I've replaced the directory where the application is installed with $APPDIR)
And here's what I see in the developer tools console:
```
workbench.main.js:63 There was an issue running a git operation.
Please review the output or use a console to check the state of
your repository.: Error: There was an issue running a git operation.
Please review the output or use a console to check the state of
your repository.
at Object.S [as create] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:10:2854)
at file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:62:16688
at Object.p [as _notify] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:181)
at Object.__dirname.undefined.F.enter (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:3509)
at __dirname.undefined.t.Class.define._run (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4830)
at __dirname.undefined.t.Class.define._chainedError (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4189)
at n (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:2017)
at Object.p [as _notify] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:181)
at Object.__dirname.undefined.F.enter (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:3509)
at __dirname.undefined.t.Class.define._run (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4830)e.doShow @ workbench.main.js:63
```
And some more version info:
```
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:26:42.359Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
```
|
completed
|
HTTPS Authentication not working on Linux On VS Code 0.10.6, when trying to sync changes in a HTTPS-backed Git repository, I get an error message which expands to [1] when I click 'show output', if VS Code was run from the desktop environment. If I close VS Code and run it from the terminal instead, I get the username and password prompts _on the terminal_ and typing from there just works (although it's obviously an uncomfortable task-switch).
[1]
```
git fetch
Missing ipc hook
error: unable to read askpass response from '$APPDIR/resources/app/out/vs/workbench/parts/git/electron-main/askpass.sh'
fatal: could not read Username for 'https://bitbucket.org': No such device or address
git pull
Missing ipc hook
error: unable to read askpass response from '$APPDIR/resources/app/out/vs/workbench/parts/git/electron-main/askpass.sh'
fatal: could not read Username for 'https://bitbucket.org': No such device or address
```
(Note: for conciseness I've replaced the directory where the application is installed with $APPDIR)
And here's what I see in the developer tools console:
```
workbench.main.js:63 There was an issue running a git operation.
Please review the output or use a console to check the state of
your repository.: Error: There was an issue running a git operation.
Please review the output or use a console to check the state of
your repository.
at Object.S [as create] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:10:2854)
at file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:62:16688
at Object.p [as _notify] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:181)
at Object.__dirname.undefined.F.enter (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:3509)
at __dirname.undefined.t.Class.define._run (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4830)
at __dirname.undefined.t.Class.define._chainedError (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4189)
at n (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:2017)
at Object.p [as _notify] (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:181)
at Object.__dirname.undefined.F.enter (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:3509)
at __dirname.undefined.t.Class.define._run (file:///$APPDIR/resources/app/out/vs/workbench/workbench.main.js:6:4830)e.doShow @ workbench.main.js:63
```
And some more version info:
```
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:26:42.359Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
```
| 907 |
[] |
0
|
False
|
|
1794
|
Keybinding widget: "<"-key not working for Swedish keyboard (Windows)
|
2016-01-05 12:00:41+00:00
|
2016-01-06 18:32:24+00:00
|
When using the Keybinding widget to edit the keybindings.json file, it will just respond with "unknown" when you try to press the key `<`. The `<` key is located between `shift` and `z` (see picture), and I belive that key isn't present on most US-keyboards.
At first I thought it was a problem with the node-native-keymap but when I try it it gives me the correct binding:
```
...
{ key_code: 'VKEY_OEM_7',
value: 'ä',
withShift: 'Ä',
withAltGr: '',
withShiftAltGr: '' },
{ key_code: 'VKEY_OEM_102',
value: '<',
withShift: '>',
withAltGr: '|',
withShiftAltGr: '' } ]
```
Not being able to bind that key makes it more or less impossible to use any vim-extensions since the `<` is used to indent.
I tried searching for a similar issue and all I could find was #1372 which is only somewhat related. I hope this isnt a duplicate.
|
completed
|
Keybinding widget: "<"-key not working for Swedish keyboard (Windows) When using the Keybinding widget to edit the keybindings.json file, it will just respond with "unknown" when you try to press the key `<`. The `<` key is located between `shift` and `z` (see picture), and I belive that key isn't present on most US-keyboards.
At first I thought it was a problem with the node-native-keymap but when I try it it gives me the correct binding:
```
...
{ key_code: 'VKEY_OEM_7',
value: 'ä',
withShift: 'Ä',
withAltGr: '',
withShiftAltGr: '' },
{ key_code: 'VKEY_OEM_102',
value: '<',
withShift: '>',
withAltGr: '|',
withShiftAltGr: '' } ]
```
Not being able to bind that key makes it more or less impossible to use any vim-extensions since the `<` is used to indent.
I tried searching for a similar issue and all I could find was #1372 which is only somewhat related. I hope this isnt a duplicate.
| 340 |
[] |
0
|
False
|
|
1786
|
Don't ship signing debug logs on Windows
|
2016-01-05 10:30:11+00:00
|
2016-03-08 14:56:04+00:00
|
My install dir is full with these:
|
completed
|
Don't ship signing debug logs on Windows My install dir is full with these:
| 75 |
[] |
0
|
False
|
|
1785
|
Can't create a tsconfig.json file anymore
|
2016-01-05 10:18:22+00:00
|
2016-01-05 14:48:49+00:00
|
- new workspace
- create folder app
- try to create tsconfig.json
Observe: after typing tscon you see
|
completed
|
Can't create a tsconfig.json file anymore - new workspace
- create folder app
- try to create tsconfig.json
Observe: after typing tscon you see
| 94 |
[] |
0
|
False
|
|
1778
|
[less] mixins ") expected" errors
|
2016-01-04 22:38:36+00:00
|
2016-07-20 16:27:25+00:00
|
When editing a **.less** file unexpected errors show when working with mixins. These errors show when using a mixin with a named parameter.
**VS Code version:**
0.10.6
**Code:**
``` less
.mixin(@a, @b) {
content: @a + @b;
}
.test {
.mixin(@b: 1);
}
```
|
completed
|
[less] mixins ") expected" errors When editing a **.less** file unexpected errors show when working with mixins. These errors show when using a mixin with a named parameter.
**VS Code version:**
0.10.6
**Code:**
``` less
.mixin(@a, @b) {
content: @a + @b;
}
.test {
.mixin(@b: 1);
}
```
| 151 |
[] |
0
|
False
|
|
1773
|
"Duplicate function implementation." Error underlining
|
2016-01-04 17:40:01+00:00
|
2016-03-14 08:49:55+00:00
|
When a JavaScript function is defined and committed to git, vscode takes further changes to the file and incorrectly notifies the user of a duplicate function implementation because of the older git version of the code and the edited version are thought to be different functions by vscode. After the change to the file is committed to git, the incorrect error underlining goes away.
|
completed
|
"Duplicate function implementation." Error underlining When a JavaScript function is defined and committed to git, vscode takes further changes to the file and incorrectly notifies the user of a duplicate function implementation because of the older git version of the code and the edited version are thought to be different functions by vscode. After the change to the file is committed to git, the incorrect error underlining goes away.
| 93 |
[] |
0
|
False
|
|
1769
|
No Intellisense with package.json
|
2016-01-04 15:28:30+00:00
|
2016-01-05 13:22:36+00:00
|
I have created a `package.json` file using `npm`. When opening it in VS Code I don't get any Intellisense whatsoever.
What's wrong?
|
completed
|
No Intellisense with package.json I have created a `package.json` file using `npm`. When opening it in VS Code I don't get any Intellisense whatsoever.
What's wrong?
| 102 |
[] |
0
|
False
|
|
1763
|
OpenAnythingHandler throws errors
|
2016-01-04 09:35:22+00:00
|
2016-01-04 12:58:25+00:00
|
```
Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}e.onUnexpectedError @ workbench.main.js:91
workbench.main.js:67 Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}: Error: Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}
at file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:22731
at __dirname.undefined.t.Class.define.done (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:6:23141)
at t.onType (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:22533)
at Object.quickOpenWidget.quickOpenWidget.d.QuickOpenWidget.onType (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:20126)
at e.doShowWithPrefix (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:26:18036)
at e.show (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:26:17864)
at t.show (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:20648)
at t.run (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:64:31858)
at file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:64:14730
at __dirname.undefined.t.Class.define.then (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:6:24063)
```
|
completed
|
OpenAnythingHandler throws errors ```
Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}e.onUnexpectedError @ workbench.main.js:91
workbench.main.js:67 Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}: Error: Unable to instanciate quick open handler vs/workbench/parts/search/browser/openAnythingHandler - OpenSymbolHandler: {}
at file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:22731
at __dirname.undefined.t.Class.define.done (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:6:23141)
at t.onType (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:22533)
at Object.quickOpenWidget.quickOpenWidget.d.QuickOpenWidget.onType (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:20126)
at e.doShowWithPrefix (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:26:18036)
at e.show (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:26:17864)
at t.show (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:71:20648)
at t.run (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:64:31858)
at file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:64:14730
at __dirname.undefined.t.Class.define.then (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:6:24063)
```
| 691 |
[] |
0
|
False
|
|
1762
|
AutoSave setting is lost
|
2016-01-04 09:33:21+00:00
|
2016-01-06 08:45:37+00:00
|
The now deprecated Auto Save setting isn't preserved by the latest changes to move it into user-settings. That's sort of data-loss and the setting should be populated with my old choice of what I had selected (Auto Save|!Auto Save).
|
completed
|
AutoSave setting is lost The now deprecated Auto Save setting isn't preserved by the latest changes to move it into user-settings. That's sort of data-loss and the setting should be populated with my old choice of what I had selected (Auto Save|!Auto Save).
| 70 |
[] |
0
|
False
|
|
1757
|
Previous state upon startup not restored
|
2016-01-03 21:32:13+00:00
|
2016-01-05 17:01:04+00:00
|
Have the ability to remember the previous state of the editor upon startup.
I used this with electron:
storage.js
```
var app = require('app');
var fs = require('fs');
var path = require('path');
var data = null;
var dataFilePath = path.join(app.getPath('userData'), 'data.json');
function load() {
if (data !== null) {
return;
}
if (!fs.existsSync(dataFilePath)) {
data = {};
return;
}
data = JSON.parse(fs.readFileSync(dataFilePath, 'utf-8'));
}
function save() {
fs.writeFileSync(dataFilePath, JSON.stringify(data));
}
exports.set = function (key, value) {
load();
data[key] = value;
save();
}
exports.get = function (key) {
load();
var value = null;
if (key in data) {
value = data[key];
}
return value;
}
exports.unset = function (key) {
load();
if (key in data) {
delete data[key];
save();
}
}
```
Then do something like this:
```
var storage = require('storage');
app.on('ready', function () {
// Create the browser window.
var lastWindowState = storage.get("lastWindowState");
if (lastWindowState === null) {
lastWindowState = {
width: 1024,
height: 768,
maximized: false
}
}
mainWindow = new BrowserWindow({
x: lastWindowState.x,
y: lastWindowState.y,
width: lastWindowState.width,
height: lastWindowState.height,
minWidth: 800,
minHeight: 600
});
mainWindow.on('close', function () {
var bounds = mainWindow.getBounds();
storage.set("lastWindowState", {
x: bounds.x,
y: bounds.y,
width: bounds.width,
height: bounds.height,
maximized: mainWindow.isMaximized()
});
});
});
```
|
completed
|
Previous state upon startup not restored Have the ability to remember the previous state of the editor upon startup.
I used this with electron:
storage.js
```
var app = require('app');
var fs = require('fs');
var path = require('path');
var data = null;
var dataFilePath = path.join(app.getPath('userData'), 'data.json');
function load() {
if (data !== null) {
return;
}
if (!fs.existsSync(dataFilePath)) {
data = {};
return;
}
data = JSON.parse(fs.readFileSync(dataFilePath, 'utf-8'));
}
function save() {
fs.writeFileSync(dataFilePath, JSON.stringify(data));
}
exports.set = function (key, value) {
load();
data[key] = value;
save();
}
exports.get = function (key) {
load();
var value = null;
if (key in data) {
value = data[key];
}
return value;
}
exports.unset = function (key) {
load();
if (key in data) {
delete data[key];
save();
}
}
```
Then do something like this:
```
var storage = require('storage');
app.on('ready', function () {
// Create the browser window.
var lastWindowState = storage.get("lastWindowState");
if (lastWindowState === null) {
lastWindowState = {
width: 1024,
height: 768,
maximized: false
}
}
mainWindow = new BrowserWindow({
x: lastWindowState.x,
y: lastWindowState.y,
width: lastWindowState.width,
height: lastWindowState.height,
minWidth: 800,
minHeight: 600
});
mainWindow.on('close', function () {
var bounds = mainWindow.getBounds();
storage.set("lastWindowState", {
x: bounds.x,
y: bounds.y,
width: bounds.width,
height: bounds.height,
maximized: mainWindow.isMaximized()
});
});
});
```
| 542 |
[] |
0
|
False
|
|
1748
|
Documentation: Extension Manifest doesn't exist
|
2016-01-02 23:34:19+00:00
|
2016-01-04 22:59:35+00:00
|
The FAQ in the [Customize Visual Studio Code](https://code.visualstudio.com/docs/customization/overview) page points to a non-existing [Extension Manifest](https://code.visualstudio.com/docs/extensions/extension-manifest) page.
Clicking the link yields a 404.
|
completed
|
Documentation: Extension Manifest doesn't exist The FAQ in the [Customize Visual Studio Code](https://code.visualstudio.com/docs/customization/overview) page points to a non-existing [Extension Manifest](https://code.visualstudio.com/docs/extensions/extension-manifest) page.
Clicking the link yields a 404.
| 94 |
[] |
0
|
False
|
|
1747
|
insertSpaces = auto, new file, first indentation, tab not possible.
|
2016-01-02 21:59:50+00:00
|
2016-03-15 08:46:42+00:00
|
When `insertSpaces = auto` is set and you create a new file, pressing the tab key will insert spaces rather than a tab character. This is a problematic default because it means there is no easy way to actually get the first tab into the file so the `auto` can start learning what the file's indentation mechanism is. If you want space indent, you can simply press the space bar a few times to start the learning process. In order to start a new file with tab indentation though you (currently) need to go find another file with a tab in it, copy the tab, and paste it into the new file.
I recommend having the fallback behavior for an empty file be that the space bar inserts spaces and the tab key inserts tabs. This way both camps (spaces and tabs) have the ability to reasonably start new files when in auto-mode.
|
completed
|
insertSpaces = auto, new file, first indentation, tab not possible. When `insertSpaces = auto` is set and you create a new file, pressing the tab key will insert spaces rather than a tab character. This is a problematic default because it means there is no easy way to actually get the first tab into the file so the `auto` can start learning what the file's indentation mechanism is. If you want space indent, you can simply press the space bar a few times to start the learning process. In order to start a new file with tab indentation though you (currently) need to go find another file with a tab in it, copy the tab, and paste it into the new file.
I recommend having the fallback behavior for an empty file be that the space bar inserts spaces and the tab key inserts tabs. This way both camps (spaces and tabs) have the ability to reasonably start new files when in auto-mode.
| 213 |
[] |
0
|
False
|
|
1732
|
problem with tasks.json and typescript compiler under Ubuntu 14.04
|
2016-01-01 19:37:14+00:00
|
2016-01-06 08:40:29+00:00
|
I have typescript installed globally but after editing tasks.json and try to run tsc command from vscode it doesn't appear in the list.If I run tsc commands from the terminal it works.
|
completed
|
problem with tasks.json and typescript compiler under Ubuntu 14.04 I have typescript installed globally but after editing tasks.json and try to run tsc command from vscode it doesn't appear in the list.If I run tsc commands from the terminal it works.
| 68 |
[] |
0
|
False
|
|
1729
|
ProblemMatcher freezes VSCode on multiline problem output
|
2016-01-01 07:00:21+00:00
|
2016-01-04 10:13:50+00:00
|
Attempt to run a python program using a single line problem matcher. For example, use the tasks.json from http://stackoverflow.com/questions/29987840/how-to-execute-python-code-from-within-visual-studio-code, except make it a test command or build command so you can run with a shortcut. Run on an app.py file containing some error, like it only contains the code `1.foo`.
The problem matcher defined in the task.json only works with single line error output, but Python delivers multiline output. I assume this is what is causing VSCode to freeze. It (at least for me) can't be closed except by killing the process.
I'm running the latest VSCode version on Windows 10.
|
completed
|
ProblemMatcher freezes VSCode on multiline problem output Attempt to run a python program using a single line problem matcher. For example, use the tasks.json from http://stackoverflow.com/questions/29987840/how-to-execute-python-code-from-within-visual-studio-code, except make it a test command or build command so you can run with a shortcut. Run on an app.py file containing some error, like it only contains the code `1.foo`.
The problem matcher defined in the task.json only works with single line error output, but Python delivers multiline output. I assume this is what is causing VSCode to freeze. It (at least for me) can't be closed except by killing the process.
I'm running the latest VSCode version on Windows 10.
| 197 |
[] |
0
|
False
|
|
1726
|
Unable to input "line break" character in search box
|
2015-12-31 17:52:52+00:00
|
2016-01-05 09:15:47+00:00
|
OS: Mac OS X 10.10.5
Visual Studio Code version: 0.10.6 (a80232bbcfe8a5cdad1ebc98638673d9dcb02458)
Description:
1. In a file I was editing, I tried to search how many "line break" characters in the file;
2. I was not sure if the "line break" character is CRLF/CR/LF, so I tried to copy & paste the "line break" character I selected to the search box;
3. Failed, unable to paste it to search box.
Related discussion:
http://stackoverflow.com/questions/30351529/find-and-replace-new-line-in-visual-studio-code
|
completed
|
Unable to input "line break" character in search box OS: Mac OS X 10.10.5
Visual Studio Code version: 0.10.6 (a80232bbcfe8a5cdad1ebc98638673d9dcb02458)
Description:
1. In a file I was editing, I tried to search how many "line break" characters in the file;
2. I was not sure if the "line break" character is CRLF/CR/LF, so I tried to copy & paste the "line break" character I selected to the search box;
3. Failed, unable to paste it to search box.
Related discussion:
http://stackoverflow.com/questions/30351529/find-and-replace-new-line-in-visual-studio-code
| 171 |
[] |
0
|
False
|
|
1721
|
File picker: can end up showing the same file twice
|
2015-12-31 06:55:36+00:00
|
2016-01-04 09:57:40+00:00
|
When searching for a workspace relative path that is not filtered by exclude rules.
|
completed
|
File picker: can end up showing the same file twice When searching for a workspace relative path that is not filtered by exclude rules.
| 33 |
[] |
0
|
False
|
|
1719
|
VS code doesnot display some UTF-8 characters
|
2015-12-31 01:59:40+00:00
|
2016-05-15 17:06:19+00:00
|
I use VS code for Windows, version 0.10.6.
VS code does not display some UTF-8 characters like '⦃' and '⟪'.
(Notepad and editor of VS 2015 Community can display that characters.)
|
completed
|
VS code doesnot display some UTF-8 characters I use VS code for Windows, version 0.10.6.
VS code does not display some UTF-8 characters like '⦃' and '⟪'.
(Notepad and editor of VS 2015 Community can display that characters.)
| 58 |
[] |
0
|
False
|
|
1712
|
IntelliSense: most relevant result is not revealed
|
2015-12-30 14:22:05+00:00
|
2016-01-04 14:50:34+00:00
|
When I have a node.js import for "path" and type "path", the element is not revealed:
|
completed
|
IntelliSense: most relevant result is not revealed When I have a node.js import for "path" and type "path", the element is not revealed:
| 90 |
[] |
0
|
False
|
|
1710
|
Diagnostics with severity Hint and Information have no visual indication in UI
|
2015-12-30 13:08:14+00:00
|
2016-01-23 13:05:21+00:00
|
Diagnostics created from an extension with `DiagnosticSeverity.Hint` or `DiagnosticSeverity.Information` have no indication in the UI. They show up very gray in the Errors/Warning selector (ctrl+m) and do not show indicators in the status bar and are not underlined in the editor.
|
completed
|
Diagnostics with severity Hint and Information have no visual indication in UI Diagnostics created from an extension with `DiagnosticSeverity.Hint` or `DiagnosticSeverity.Information` have no indication in the UI. They show up very gray in the Errors/Warning selector (ctrl+m) and do not show indicators in the status bar and are not underlined in the editor.
| 97 |
[] |
0
|
False
|
|
1708
|
workspace.applyEdit fails in git view
|
2015-12-30 10:43:09+00:00
|
2016-02-02 08:26:02+00:00
|
I have a code action that performs a WorkspaceEdit which works just fine in the normal view but fails in the diff view.
Code:
``` javascript
let edit = new vscode.WorkspaceEdit();
edit.replace(uri, range, replacementText);
vscode.workspace.applyEdit(edit);
```
Message:
TypeError: i.getModel(...).getAssociatedResource is not a function
Stack:
TypeError: i.getModel(...).getAssociatedResource is not a function\n at Object.a [as finish](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:36:9471)\n at Object.d [as bulkEdit](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:36:9143)\n at e.applyWorkspaceEdit (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:61:18416)\n at t.e.handle (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:52:3220)\n at a (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:38:12357)\n at Object.h.handle (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:38:12921)\n at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:67:5098\n at ChildProcess.<anonymous> (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:67:7608)\n at emitTwo (events.js:87:13)\n at ChildProcess.emit (events.js:172:7)
|
completed
|
workspace.applyEdit fails in git view I have a code action that performs a WorkspaceEdit which works just fine in the normal view but fails in the diff view.
Code:
``` javascript
let edit = new vscode.WorkspaceEdit();
edit.replace(uri, range, replacementText);
vscode.workspace.applyEdit(edit);
```
Message:
TypeError: i.getModel(...).getAssociatedResource is not a function
Stack:
TypeError: i.getModel(...).getAssociatedResource is not a function\n at Object.a [as finish](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:36:9471)\n at Object.d [as bulkEdit](file:///C:/Program Files %28x86%29/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:36:9143)\n at e.applyWorkspaceEdit (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:61:18416)\n at t.e.handle (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:52:3220)\n at a (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:38:12357)\n at Object.h.handle (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:38:12921)\n at file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:67:5098\n at ChildProcess.<anonymous> (file:///C:/Program Files (x86)/Microsoft VS Code/resources/app/out/vs/workbench/workbench.main.js:67:7608)\n at emitTwo (events.js:87:13)\n at ChildProcess.emit (events.js:172:7)
| 579 |
[] |
0
|
False
|
|
1704
|
cannot launch code from command line using Git Bash on Windows
|
2015-12-30 02:50:33+00:00
|
2016-02-25 15:53:35+00:00
|
`code .` works fine in cmd.exe on Windows 10, but fails with `command not found` when in Git Bash.
Please add built-in support for launching code from the Git Bash command line. This works with atom out of the box.
|
completed
|
cannot launch code from command line using Git Bash on Windows `code .` works fine in cmd.exe on Windows 10, but fails with `command not found` when in Git Bash.
Please add built-in support for launching code from the Git Bash command line. This works with atom out of the box.
| 74 |
[] |
0
|
False
|
|
1703
|
Thread exited event ignored
|
2015-12-30 00:14:19+00:00
|
2016-04-21 19:39:02+00:00
|
Even though clearly an thread event with `reason: "exited"` is sent, VS Code does not update the UI to remove the exited thread:
last communication:
```
-> continueRequest
{ type: 'request',
seq: 21,
command: 'continue',
arguments: { threadId: 2 } }
<- continueResponse
Response {
seq: 0,
type: 'response',
request_seq: 21,
command: 'continue',
success: true }
<- threadEvent
ThreadEvent {
seq: 0,
type: 'event',
event: 'thread',
body: { reason: 'exited', threadId: 2 } }
```
When a stack frame inside the dead thread is clicked VS Code tries to request the variables inside a thread that doesn't exist anymore.
Even weirder, the threads even keep showing even after the debug session ended:
|
completed
|
Thread exited event ignored Even though clearly an thread event with `reason: "exited"` is sent, VS Code does not update the UI to remove the exited thread:
last communication:
```
-> continueRequest
{ type: 'request',
seq: 21,
command: 'continue',
arguments: { threadId: 2 } }
<- continueResponse
Response {
seq: 0,
type: 'response',
request_seq: 21,
command: 'continue',
success: true }
<- threadEvent
ThreadEvent {
seq: 0,
type: 'event',
event: 'thread',
body: { reason: 'exited', threadId: 2 } }
```
When a stack frame inside the dead thread is clicked VS Code tries to request the variables inside a thread that doesn't exist anymore.
Even weirder, the threads even keep showing even after the debug session ended:
| 321 |
[] |
0
|
False
|
|
1702
|
buffer newly created breakpoints until initialize request is received
|
2015-12-29 23:57:34+00:00
|
2016-01-04 10:48:06+00:00
|
A debug adapter is free to request persisted breakpoints at any time by sending an "initialize" request. If another breakpoint is created before the "initialize" request has arrived, the breakpoint is directly sent to the adapter without waiting for the "initialize" request. This is a bug. We should buffer these breakpoints and send them to the adapter only upon receipt of the "initialize".
cc @felixfbecker
|
completed
|
buffer newly created breakpoints until initialize request is received A debug adapter is free to request persisted breakpoints at any time by sending an "initialize" request. If another breakpoint is created before the "initialize" request has arrived, the breakpoint is directly sent to the adapter without waiting for the "initialize" request. This is a bug. We should buffer these breakpoints and send them to the adapter only upon receipt of the "initialize".
cc @felixfbecker
| 119 |
[] |
0
|
False
|
|
1701
|
Break reason is shared between threads
|
2015-12-29 23:50:06+00:00
|
2016-01-04 14:55:12+00:00
|
If one thread breaks on exception, and the other breaks on a breakpoint, whatever reason came last will always be what is shown in the UI.
|
completed
|
Break reason is shared between threads If one thread breaks on exception, and the other breaks on a breakpoint, whatever reason came last will always be what is shown in the UI.
| 102 |
[] |
0
|
False
|
|
1700
|
VS Code does not honor success: false for VariableRequests
|
2015-12-29 23:27:27+00:00
|
2016-01-04 11:58:59+00:00
|
A bug I picked up during development. This is an screenshot showing how VS Code displays an error that was send through `sendErrorResponse` as a result for the variable, when it should really show an error message for the user.
Here are my communication logs:
```
-> variablesRequest
{ type: 'request',
seq: 10,
command: 'variables',
arguments: { variablesReference: 1 } }
<- variablesResponse
Response {
seq: 0,
type: 'response',
request_seq: 10,
command: 'variables',
success: false,
message: 'request \'variables\': test',
body:
{ error:
{ id: 123,
format: 'request \'variables\': test',
showUser: true } } }
```
|
completed
|
VS Code does not honor success: false for VariableRequests A bug I picked up during development. This is an screenshot showing how VS Code displays an error that was send through `sendErrorResponse` as a result for the variable, when it should really show an error message for the user.
Here are my communication logs:
```
-> variablesRequest
{ type: 'request',
seq: 10,
command: 'variables',
arguments: { variablesReference: 1 } }
<- variablesResponse
Response {
seq: 0,
type: 'response',
request_seq: 10,
command: 'variables',
success: false,
message: 'request \'variables\': test',
body:
{ error:
{ id: 123,
format: 'request \'variables\': test',
showUser: true } } }
```
| 257 |
[] |
0
|
False
|
|
1698
|
Extension broke 10.3 to 10.5 => Objects passed as command arguments are now stripped of functions
|
2015-12-29 22:49:04+00:00
|
2016-01-05 09:38:14+00:00
|
I have an extension that works in version 0.10.3 but does not work in 0.10.5+.
The cause of this breakage is that functions on objects passed in the `arguments` array of a `Command` were available when executing the actions in 0.10.3 but are not available in 10.5+
This is illustrated in the following example:
``` javascript
class Repro implements vscode.CodeActionProvider {
public commandId = 'hoovercj.reproCommand';
private command;
constructor() {
this.command = vscode.commands.registerCommand(this.commandId, this.runCodeAction, this);
}
public provideCodeActions(document: vscode.TextDocument, range: vscode.Range, context: vscode.CodeActionContext, token: vscode.CancellationToken): vscode.Command[] {
return [<vscode.Command>{
title: "Broken Command",
command: this.commandId,
arguments: [document, {
broken: () => { return 5; },
works: 5
}]
}];
}
public runCodeAction(document: vscode.TextDocument, test:any) {
try {
test.works;
test.broken();
document.getText();
} catch (error) {
// This should show up in 10.5+ but should not show up in 10.3
vscode.window.showErrorMessage(error);
}
}
```
|
completed
|
Extension broke 10.3 to 10.5 => Objects passed as command arguments are now stripped of functions I have an extension that works in version 0.10.3 but does not work in 0.10.5+.
The cause of this breakage is that functions on objects passed in the `arguments` array of a `Command` were available when executing the actions in 0.10.3 but are not available in 10.5+
This is illustrated in the following example:
``` javascript
class Repro implements vscode.CodeActionProvider {
public commandId = 'hoovercj.reproCommand';
private command;
constructor() {
this.command = vscode.commands.registerCommand(this.commandId, this.runCodeAction, this);
}
public provideCodeActions(document: vscode.TextDocument, range: vscode.Range, context: vscode.CodeActionContext, token: vscode.CancellationToken): vscode.Command[] {
return [<vscode.Command>{
title: "Broken Command",
command: this.commandId,
arguments: [document, {
broken: () => { return 5; },
works: 5
}]
}];
}
public runCodeAction(document: vscode.TextDocument, test:any) {
try {
test.works;
test.broken();
document.getText();
} catch (error) {
// This should show up in 10.5+ but should not show up in 10.3
vscode.window.showErrorMessage(error);
}
}
```
| 361 |
[] |
0
|
False
|
|
1693
|
Assign accelerator keys to dialog buttons
|
2015-12-29 17:55:17+00:00
|
2016-01-04 09:57:40+00:00
|
There are no shortcut keys defined for the dialog that pops up asking "Do you want to save the changes you made to..." when closing Code. The keys S, N and possibly C should save, abort save or abort closing.
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:34:58.895Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
|
completed
|
Assign accelerator keys to dialog buttons There are no shortcut keys defined for the dialog that pops up asking "Do you want to save the changes you made to..." when closing Code. The keys S, N and possibly C should save, abort save or abort closing.
Version 0.10.6
Commit a80232bbcfe8a5cdad1ebc98638673d9dcb02458
Date 2015-12-19T11:34:58.895Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
| 180 |
[] |
0
|
False
|
|
1691
|
Activated linter does not go away when switching language mode
|
2015-12-29 17:22:04+00:00
|
2016-03-14 08:50:13+00:00
|
**Steps to reproduce**
1. Create an invalid file featuring invalid javascript, such as:
```
# I'm invalid
```
2. Switch language mode to javascript (command palette -> `"lang"` -> <kbd>enter</kbd> -> `"javascript"` -> <kbd>enter</kbd>)
3. Observe red underlines indicating linter errors
4. Switch language mode to something other than javascript
**Expected**
The javascript linter is deactivated
**Actual**
The javascript linter errors remain
|
completed
|
Activated linter does not go away when switching language mode **Steps to reproduce**
1. Create an invalid file featuring invalid javascript, such as:
```
# I'm invalid
```
2. Switch language mode to javascript (command palette -> `"lang"` -> <kbd>enter</kbd> -> `"javascript"` -> <kbd>enter</kbd>)
3. Observe red underlines indicating linter errors
4. Switch language mode to something other than javascript
**Expected**
The javascript linter is deactivated
**Actual**
The javascript linter errors remain
| 133 |
[] |
0
|
False
|
|
1687
|
VSC 10.6 does not allow to attach debugger to running Electron app (working great with 10.3)
|
2015-12-29 13:22:17+00:00
|
2016-01-19 10:31:39+00:00
|
VSC 10.6 does not allow to attach the debugger to a running Electron (0.36.2) app.
I was able to downgrade VSC by downloading from here to version 10.3: https://github.com/Microsoft/vscode/wiki/Previous-Releases.
VSC 10.3 is allowing to attach the debugger to a running Electron app with these simple settings:
{
"name": "Attach",
"request": "attach",
"type": "node",
// TCP/IP address. Default is "localhost".
//"address": "localhost",
// Port to attach to.
"port": 5858,
"sourceMaps": false
}
Thanks for your support.
|
completed
|
VSC 10.6 does not allow to attach debugger to running Electron app (working great with 10.3) VSC 10.6 does not allow to attach the debugger to a running Electron (0.36.2) app.
I was able to downgrade VSC by downloading from here to version 10.3: https://github.com/Microsoft/vscode/wiki/Previous-Releases.
VSC 10.3 is allowing to attach the debugger to a running Electron app with these simple settings:
{
"name": "Attach",
"request": "attach",
"type": "node",
// TCP/IP address. Default is "localhost".
//"address": "localhost",
// Port to attach to.
"port": 5858,
"sourceMaps": false
}
Thanks for your support.
| 194 |
[] |
0
|
False
|
|
1684
|
The text goes beyond the window
|
2015-12-29 01:07:01+00:00
|
2017-04-05 13:31:24+00:00
|
Open any text file and resize window in the horizontal direction.
|
completed
|
The text goes beyond the window Open any text file and resize window in the horizontal direction.
| 84 |
[] |
0
|
False
|
|
1678
|
[bat] Fix batch syntax
|
2015-12-28 19:10:23+00:00
|
2016-01-08 14:19:24+00:00
|
Fixes some issues with batch syntax, addressing #487
- `rem` comments are properly detected
- variables are properly parsed, including
- `%regular_variables%`
- `!delay_expanded_variables!`
- Script parameters (`%1`, `%~dp0`, etc.)
- Loop induction variables (`%%f`, `%%~nxf`, etc.)
- Incomplete strings now terminate at end of line, fixing cases like the following:
``` batch
echo incomplete " string
echo broken line, treated as string
```
|
[bat] Fix batch syntax Fixes some issues with batch syntax, addressing #487
- `rem` comments are properly detected
- variables are properly parsed, including
- `%regular_variables%`
- `!delay_expanded_variables!`
- Script parameters (`%1`, `%~dp0`, etc.)
- Loop induction variables (`%%f`, `%%~nxf`, etc.)
- Incomplete strings now terminate at end of line, fixing cases like the following:
``` batch
echo incomplete " string
echo broken line, treated as string
```
| 154 |
[] |
0
|
False
|
||
1669
|
[C++] final and override keywords are not correctly identified
|
2015-12-27 16:58:46+00:00
|
2017-02-22 22:09:56+00:00
|
The C++11 specifiers [`final`](http://en.cppreference.com/w/cpp/language/final) and [`override`](http://en.cppreference.com/w/cpp/language/override) are missing in the C++ syntax file.
They are context specific keywords, so they must not always be classified as a keyword.
Ironically they are present in the [C syntax](https://github.com/Microsoft/vscode/blob/master/extensions/cpp/syntaxes/c.plist#L435) file with some checks for the correct context.
This check fails for some cases though. These three are currently missing in Code:
``` c++
class deriv final : base {
void meth1() final;
void meth2() override;
}
```
- final and override in class declarations
- final classes ... GitHub seems to be missing that one too :smile:
|
completed
|
[C++] final and override keywords are not correctly identified The C++11 specifiers [`final`](http://en.cppreference.com/w/cpp/language/final) and [`override`](http://en.cppreference.com/w/cpp/language/override) are missing in the C++ syntax file.
They are context specific keywords, so they must not always be classified as a keyword.
Ironically they are present in the [C syntax](https://github.com/Microsoft/vscode/blob/master/extensions/cpp/syntaxes/c.plist#L435) file with some checks for the correct context.
This check fails for some cases though. These three are currently missing in Code:
``` c++
class deriv final : base {
void meth1() final;
void meth2() override;
}
```
- final and override in class declarations
- final classes ... GitHub seems to be missing that one too :smile:
| 247 |
[] |
0
|
False
|
|
1668
|
Markdown previewing for code blocks breaks when 1st line is square bracket
|
2015-12-27 08:50:48+00:00
|
2016-09-28 22:25:41+00:00
|
A picture speaks a thousand words. First screenshot, Markdown previewing is incorrect and ordered numbering is subsequently broken also as a result of the first line of the code starting with an open square bracket. When the open square bracket is replaced with another character (a number 1 in the second screenshot), the preview works fine.
|
completed
|
Markdown previewing for code blocks breaks when 1st line is square bracket A picture speaks a thousand words. First screenshot, Markdown previewing is incorrect and ordered numbering is subsequently broken also as a result of the first line of the code starting with an open square bracket. When the open square bracket is replaced with another character (a number 1 in the second screenshot), the preview works fine.
| 207 |
[] |
0
|
False
|
|
1667
|
${file} variable should change when active editor pane switches to a different file
|
2015-12-27 07:34:14+00:00
|
2015-12-28 09:37:50+00:00
|
It appears that the `${file}` variable can be used in `launch.json` configurations to determine the "program" to be run when the user starts the debugger. A couple users of the PowerShell extension have discovered that this variable will have the file path of the first opened file in the workspace. However, if they switch active files this variable does not change, meaning that the debugger will always run that first file. See more discussion here:
https://github.com/PowerShell/vscode-powershell/commit/a613d5eafa2f014ce0b2b5b857eb60d4e6d11fb8
It would be nice if this variable got updated dynamically so that the user can run the debugger against the currently active file without having to manually edit their `launch.json` file each time. This is a pretty common practice when developing PowerShell scripts.
|
completed
|
${file} variable should change when active editor pane switches to a different file It appears that the `${file}` variable can be used in `launch.json` configurations to determine the "program" to be run when the user starts the debugger. A couple users of the PowerShell extension have discovered that this variable will have the file path of the first opened file in the workspace. However, if they switch active files this variable does not change, meaning that the debugger will always run that first file. See more discussion here:
https://github.com/PowerShell/vscode-powershell/commit/a613d5eafa2f014ce0b2b5b857eb60d4e6d11fb8
It would be nice if this variable got updated dynamically so that the user can run the debugger against the currently active file without having to manually edit their `launch.json` file each time. This is a pretty common practice when developing PowerShell scripts.
| 234 |
[] |
0
|
False
|
|
1661
|
Issue in indentation when formatting consecutive objects
|
2015-12-26 11:41:24+00:00
|
2016-01-04 10:45:40+00:00
|
There's a very annoying issue when hitting "format code" in a TS file. Here's an example:
``` ts
[{
}, {
}]
// or
fn({
}, {
})
```
becomes:
``` ts
[{
}, {
}]
// or
fn({
}, {
})
```
This gets really annoying when you have large nested objects containing things like functions etc...
|
completed
|
Issue in indentation when formatting consecutive objects There's a very annoying issue when hitting "format code" in a TS file. Here's an example:
``` ts
[{
}, {
}]
// or
fn({
}, {
})
```
becomes:
``` ts
[{
}, {
}]
// or
fn({
}, {
})
```
This gets really annoying when you have large nested objects containing things like functions etc...
| 110 |
[] |
0
|
False
|
|
1659
|
[css] @namespace is not syntax highlighted
|
2015-12-26 10:43:28+00:00
|
2017-02-22 21:48:25+00:00
|
Works correctly in the parser for linting and in Intellisense, but isn't syntax highlighted as missing from css.plist
Syntax should be:
namespace
: NAMESPACE_SYM S\* [namespace_prefix S_]? [STRING|URI] S_ ';' S*
;
namespace_prefix
: IDENT
;
My knowledge of the syntax of css.plist and regexp isn't good enough at the moment to work out how to add the optional IDENT, as there is no predefined ident like there is for strings, etc. I know how to highlight the @namespace and string component though.
I figure the IDENT should be coloured the same as @namespace as that is how the media type token is coloured for '@media media-type'
|
completed
|
[css] @namespace is not syntax highlighted Works correctly in the parser for linting and in Intellisense, but isn't syntax highlighted as missing from css.plist
Syntax should be:
namespace
: NAMESPACE_SYM S\* [namespace_prefix S_]? [STRING|URI] S_ ';' S*
;
namespace_prefix
: IDENT
;
My knowledge of the syntax of css.plist and regexp isn't good enough at the moment to work out how to add the optional IDENT, as there is no predefined ident like there is for strings, etc. I know how to highlight the @namespace and string component though.
I figure the IDENT should be coloured the same as @namespace as that is how the media type token is coloured for '@media media-type'
| 253 |
[] |
0
|
False
|
|
1658
|
Patch gave me issues that persist in fresh install...
|
2015-12-26 07:35:37+00:00
|
2016-02-03 11:00:56+00:00
|
[C:/Users/Robbie Blair/.vscode/extensions/eg2.tslint]: Cannot read file C:/Users/Robbie Blair/.vscode/extensions/eg2.tslint/package.json: ENOENT: no such file or directory, open 'C:\Users\Robbie Blair.vscode\extensions\eg2.tslint\package.json'
I dont know what eg2 is.. presumably if I installed the extension itd go away???
|
completed
|
Patch gave me issues that persist in fresh install... [C:/Users/Robbie Blair/.vscode/extensions/eg2.tslint]: Cannot read file C:/Users/Robbie Blair/.vscode/extensions/eg2.tslint/package.json: ENOENT: no such file or directory, open 'C:\Users\Robbie Blair.vscode\extensions\eg2.tslint\package.json'
I dont know what eg2 is.. presumably if I installed the extension itd go away???
| 143 |
[] |
0
|
False
|
|
1657
|
Don't try to content assist in comments
|
2015-12-26 06:18:27+00:00
|
2017-03-08 09:44:48+00:00
|
Don't try to content assist / perform intellisense when writing a comment. Really really annoying, when every other word pops up suggestions. Don't want it.
Dupe of #538 that got closed but not fixed really though.
|
completed
|
Don't try to content assist in comments Don't try to content assist / perform intellisense when writing a comment. Really really annoying, when every other word pops up suggestions. Don't want it.
Dupe of #538 that got closed but not fixed really though.
| 64 |
[] |
0
|
False
|
|
1656
|
[CSS] Syntax highlighting no longer works for property keyword values and functions
|
2015-12-26 03:56:25+00:00
|
2016-02-29 16:31:56+00:00
|
Before Dec update:
After:
As you can see, while the property names are highlighted, the values are the same whether it is valid or not. The data is in the css.plist file, it is just not getting read, or the colour is no longer set, for whatever reason.
|
completed
|
[CSS] Syntax highlighting no longer works for property keyword values and functions Before Dec update:
After:
As you can see, while the property names are highlighted, the values are the same whether it is valid or not. The data is in the css.plist file, it is just not getting read, or the colour is no longer set, for whatever reason.
| 196 |
[] |
0
|
False
|
|
1655
|
[CSS] Vendor prefixes are not syntax highlighted in property names
|
2015-12-26 03:49:23+00:00
|
2016-01-12 10:17:58+00:00
|
I think this is related to an issue Atom fixed in their repo:
https://github.com/atom/language-css/commit/6e3e60632f36e304e18f1f3a5581753c73286ddb
|
completed
|
[CSS] Vendor prefixes are not syntax highlighted in property names 
I think this is related to an issue Atom fixed in their repo:
https://github.com/atom/language-css/commit/6e3e60632f36e304e18f1f3a5581753c73286ddb
| 136 |
[] |
0
|
False
|
|
1654
|
[css] calc() is not in IntelliSense or syntax highlight
|
2015-12-26 03:44:14+00:00
|
2017-02-22 21:47:40+00:00
|
calc is not included in css.plist so it is not coloured:
(no values are coloured in latest Dec update but that is a different issue.)
It is also not included in the auto complete suggestions. (although as a by product of lengths being valid values, at least those parts get Intellisense inside the brackets)
" It can be used wherever <length>, <frequency>, <angle>, <time>, <number>, or <integer> values are allowed. " – http://www.w3.org/TR/css3-values/#calc-notation
|
completed
|
[css] calc() is not in IntelliSense or syntax highlight calc is not included in css.plist so it is not coloured:
(no values are coloured in latest Dec update but that is a different issue.)
It is also not included in the auto complete suggestions. (although as a by product of lengths being valid values, at least those parts get Intellisense inside the brackets)
" It can be used wherever <length>, <frequency>, <angle>, <time>, <number>, or <integer> values are allowed. " – http://www.w3.org/TR/css3-values/#calc-notation
| 234 |
[] |
0
|
False
|
|
1647
|
IntelliSense breaks when joining 'var' declarations with 'yield' keyword.
|
2015-12-25 11:57:47+00:00
|
2016-03-14 08:50:35+00:00
|
var variable1 = yield instance.generatorFunction(), variable2 = yield [[here IntelliSense stops recognizing presence of 'instance']]
|
completed
|
IntelliSense breaks when joining 'var' declarations with 'yield' keyword. var variable1 = yield instance.generatorFunction(), variable2 = yield [[here IntelliSense stops recognizing presence of 'instance']]
| 61 |
[] |
0
|
False
|
|
1646
|
Disabling windows' recycling bin causes file deleting to fail
|
2015-12-25 07:28:27+00:00
|
2015-12-28 13:07:20+00:00
|
It will fail every time showing the error:
```
Failed to move '{filename}' to the trash
```
and won't delete until you use the `Delete Permanently` option in the error message
|
completed
|
Disabling windows' recycling bin causes file deleting to fail It will fail every time showing the error:
```
Failed to move '{filename}' to the trash
```
and won't delete until you use the `Delete Permanently` option in the error message
| 63 |
[] |
0
|
False
|
|
1642
|
gulpfile.hygiene on Windows
|
2015-12-24 19:36:18+00:00
|
2016-03-04 09:44:28+00:00
|
I'm using Windows with `core.autocrlf=true` which means that files in my working directory have CRLF line endings, but are converted to LF when I commit. But I can't commit because the hygiene check fails because it sees the CRLF endings.
I got around it by converting the file to just use LF, but is there a recommended workflow for Windows environments? Working entirely in LF might work but inevitably some tool won't like that. Maybe hygiene could skip the line ending check if `core.autocrlf=true`?
|
completed
|
gulpfile.hygiene on Windows I'm using Windows with `core.autocrlf=true` which means that files in my working directory have CRLF line endings, but are converted to LF when I commit. But I can't commit because the hygiene check fails because it sees the CRLF endings.
I got around it by converting the file to just use LF, but is there a recommended workflow for Windows environments? Working entirely in LF might work but inevitably some tool won't like that. Maybe hygiene could skip the line ending check if `core.autocrlf=true`?
| 148 |
[] |
0
|
False
|
|
1636
|
Selection and selection matches highlight color
|
2015-12-24 13:17:33+00:00
|
2016-08-29 17:53:11+00:00
|
It's really hard to tell which is the selected text and which are the selection matches.
|
completed
|
Selection and selection matches highlight color 
It's really hard to tell which is the selected text and which are the selection matches.
| 82 |
[] |
0
|
False
|
|
1634
|
[sql] syntax highlighting error
|
2015-12-24 11:10:46+00:00
|
2017-02-23 20:32:17+00:00
|
Problems with ' '
|
completed
|
[sql] syntax highlighting error Problems with ' '
| 70 |
[] |
0
|
False
|
|
1632
|
javascript code analysis error by comment
|
2015-12-24 07:13:27+00:00
|
2016-03-14 08:50:55+00:00
|
|
completed
|
javascript code analysis error by comment 
| 165 |
[] |
0
|
False
|
|
1630
|
word moved the direction when arrow key pressed after type Korean letter
|
2015-12-24 06:33:35+00:00
|
2016-01-29 01:59:02+00:00
|
I've installed VSCode 0.10.6.
When I typed Korean letter, the text pane color was changed to black.
Then if I didn't put space before move my cursor, Korean words follows the cursor.
For example, if I typed {A} word then move cursor to next line, {A} is placed in next line not the previous cursor position.
|
completed
|
word moved the direction when arrow key pressed after type Korean letter I've installed VSCode 0.10.6.
When I typed Korean letter, the text pane color was changed to black.
Then if I didn't put space before move my cursor, Korean words follows the cursor.
For example, if I typed {A} word then move cursor to next line, {A} is placed in next line not the previous cursor position.
| 99 |
[] |
0
|
False
|
|
1623
|
Tab in CSS editor after colon creates errant autocomplete
|
2015-12-24 01:03:26+00:00
|
2017-04-03 14:05:20+00:00
|
**Bug:** When editing a CSS file, using the tab key after a colon inserts the characters `:;` rather than actually inserting the tab. Similar expansion bugs occur when pressing tab before the colon, or after any selector.
**What should happen:** a tab character should be inserted, or if the user has chosen to expand tabs to spaces, the appropriate number of spaces.
**Steps to reproduce:**
Enter the following code in a CSS file:
``` css
div {
font-size:12pt;
}
```
Position the cursor after the `:` and hit the tab key. Rather than `12pt` moving to the right, an extra `:;` is inserted.
**Platform:** OS X 10.11.2, Visual Studio Code 0.10.5.
I've tested this in Windows 10 on Visual Studio Community Edition, and it behaves as expected.
|
completed
|
Tab in CSS editor after colon creates errant autocomplete **Bug:** When editing a CSS file, using the tab key after a colon inserts the characters `:;` rather than actually inserting the tab. Similar expansion bugs occur when pressing tab before the colon, or after any selector.
**What should happen:** a tab character should be inserted, or if the user has chosen to expand tabs to spaces, the appropriate number of spaces.
**Steps to reproduce:**
Enter the following code in a CSS file:
``` css
div {
font-size:12pt;
}
```
Position the cursor after the `:` and hit the tab key. Rather than `12pt` moving to the right, an extra `:;` is inserted.
**Platform:** OS X 10.11.2, Visual Studio Code 0.10.5.
I've tested this in Windows 10 on Visual Studio Community Edition, and it behaves as expected.
| 216 |
[] |
0
|
False
|
|
1622
|
Output window sometimes doesn't display output
|
2015-12-24 00:30:48+00:00
|
2016-01-20 14:53:15+00:00
|
When running a task (I'm running the default build task), and the output editor panel is closed, it sometimes opens up empty. I don't notice this bug if the output editor panel is already open and I run Ctrl+Shift+B; I only notice it when the panel is closed and Ctrl+Shift+B opens it up.
This does not happen every time, but I notice it most frequently (about 90% of the time) when the task being run is an invalid command (in my case, I was using g+ rather than g++).
The only extension I have installed is C++ IntelliSense
I'm running the latest version of VSCode on Windows 10.
|
completed
|
Output window sometimes doesn't display output When running a task (I'm running the default build task), and the output editor panel is closed, it sometimes opens up empty. I don't notice this bug if the output editor panel is already open and I run Ctrl+Shift+B; I only notice it when the panel is closed and Ctrl+Shift+B opens it up.
This does not happen every time, but I notice it most frequently (about 90% of the time) when the task being run is an invalid command (in my case, I was using g+ rather than g++).
The only extension I have installed is C++ IntelliSense
I'm running the latest version of VSCode on Windows 10.
| 158 |
[] |
0
|
False
|
|
1620
|
Line indent doesn't handle leading whitespace properly
|
2015-12-23 21:46:23+00:00
|
2017-04-05 13:28:46+00:00
|
Indenting a line with leading whitespace seems to have some corners that need ironing out. It appears to be attempting something smart about tab-stop alignment, but it should really just be dumb and indent all lines the same.
e.g.
Right-justified tabular data is affected by this (e.g. output of many Powershell commands, or the robocopy usage message)
|
completed
|
Line indent doesn't handle leading whitespace properly Indenting a line with leading whitespace seems to have some corners that need ironing out. It appears to be attempting something smart about tab-stop alignment, but it should really just be dumb and indent all lines the same.
e.g.
Right-justified tabular data is affected by this (e.g. output of many Powershell commands, or the robocopy usage message)
| 341 |
[] |
0
|
False
|
|
1615
|
Relative HTML image tags in markdown are not working
|
2015-12-23 13:33:42+00:00
|
2016-09-21 01:05:02+00:00
|
I think this relates to #803 but seems to be a bit different (or an update hasn't been deployed with the fix).
I have a project that is the entire web site and within there is a folder where we draft blog posts in markdown. So the folder structure looks like this:
```
app
⌞ posts
⌞ 2016
⌞ 01
⌞ blog-slug
⌞ index.md
⌞ image.png
```
When I try to reference this image in html it appears as a broken image:
```
<img src="image.png" width="100%">
```
in dev tools I see it's looking for the image in "file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/image.png" but only references the image by name in the rendered html. (see image)
<img width="366" alt="screen shot 2015-12-23 at 8 29 27 am" src="https://cloud.githubusercontent.com/assets/129322/11977286/5a72e720-a94f-11e5-9192-6166777cb895.png">
when referenced as markdown it renders fine:
```
```
In dev tools it has the complete file path to the image.
<img width="384" alt="screen shot 2015-12-23 at 8 30 37 am" src="https://cloud.githubusercontent.com/assets/129322/11977305/7c34fe16-a94f-11e5-9d20-af16b39d0573.png">
|
completed
|
Relative HTML image tags in markdown are not working I think this relates to #803 but seems to be a bit different (or an update hasn't been deployed with the fix).
I have a project that is the entire web site and within there is a folder where we draft blog posts in markdown. So the folder structure looks like this:
```
app
⌞ posts
⌞ 2016
⌞ 01
⌞ blog-slug
⌞ index.md
⌞ image.png
```
When I try to reference this image in html it appears as a broken image:
```
<img src="image.png" width="100%">
```
in dev tools I see it's looking for the image in "file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/image.png" but only references the image by name in the rendered html. (see image)
<img width="366" alt="screen shot 2015-12-23 at 8 29 27 am" src="https://cloud.githubusercontent.com/assets/129322/11977286/5a72e720-a94f-11e5-9192-6166777cb895.png">
when referenced as markdown it renders fine:
```
```
In dev tools it has the complete file path to the image.
<img width="384" alt="screen shot 2015-12-23 at 8 30 37 am" src="https://cloud.githubusercontent.com/assets/129322/11977305/7c34fe16-a94f-11e5-9d20-af16b39d0573.png">
| 396 |
[] |
0
|
False
|
|
1609
|
Wrong indentation of block comments.
|
2015-12-23 09:51:29+00:00
|
2016-01-11 09:53:09+00:00
|
Thank you for fixed #348.
Still, there is a case that `Indent` operation for block comments is wrong.
If there is a empty line in a block comment, after the empty line, a space followed by the first `*` on every line is lost.
We would often encounter this case if `files.trimTrailingWhitespace` setting is enabled.
---
```
Version 0.10.5
Commit dfc08dc9edf6607483b193bf934d3badc3fa2e11
Date 2015-12-17T16:08:04.766Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
```
On Windows 7 Pro 64bit
|
completed
|
Wrong indentation of block comments. Thank you for fixed #348.
Still, there is a case that `Indent` operation for block comments is wrong.
If there is a empty line in a block comment, after the empty line, a space followed by the first `*` on every line is lost.
We would often encounter this case if `files.trimTrailingWhitespace` setting is enabled.
---
```
Version 0.10.5
Commit dfc08dc9edf6607483b193bf934d3badc3fa2e11
Date 2015-12-17T16:08:04.766Z
Shell 0.34.5
Renderer 45.0.2454.85
Node 4.1.1
```
On Windows 7 Pro 64bit
| 211 |
[] |
0
|
False
|
|
1607
|
Keyboard shortcuts doesn't Prevent Default Action
|
2015-12-23 08:44:53+00:00
|
2017-03-24 11:46:01+00:00
|
I have set a shortcut below:
``` json
[
{ "key": "alt+f", "command": "workbench.action.files.revealActiveFileInWindows" },
]
```
VSCode does reveal the open file in Finder, however sometimes it also print a `ƒ` character which is unexpected.
|
completed
|
Keyboard shortcuts doesn't Prevent Default Action I have set a shortcut below:
``` json
[
{ "key": "alt+f", "command": "workbench.action.files.revealActiveFileInWindows" },
]
```
VSCode does reveal the open file in Finder, however sometimes it also print a `ƒ` character which is unexpected.
| 143 |
[] |
0
|
False
|
|
1605
|
updating to vscode 0.10.5 issue with csharp-o
|
2015-12-23 08:10:39+00:00
|
2016-02-23 11:05:01+00:00
|
Looking into [repository](https://github.com/Microsoft/vscode/tree/master/extensions), there is no longer folder named **csharp-o**.
I manually deleted the folder and restarted vscode and issue is gone. So, problem looks like installer not removing that file.
|
completed
|
updating to vscode 0.10.5 issue with csharp-o Looking into [repository](https://github.com/Microsoft/vscode/tree/master/extensions), there is no longer folder named **csharp-o**.
I manually deleted the folder and restarted vscode and issue is gone. So, problem looks like installer not removing that file.
| 145 |
[] |
0
|
False
|
|
1599
|
ctrl+shift+j yields "Cannot read property 'openViewlet' of undefined"
|
2015-12-23 01:34:54+00:00
|
2015-12-23 08:40:18+00:00
|
## explanation
The default keyboard shortcuts file contains:
```
{
"key": "ctrl+shift+j",
"command": "workbench.action.search.toggleQueryDetails",
"when": "searchViewletVisible"
},
```
So, I tried it out, but got an error.
## repro
1. Open search view (via <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>f</kbd> or mouse click).
2. Attempt to use shortcut <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>j</kbd>.
3. See error message: "Cannot read property 'openViewlet' of undefined".
## supporting info
- version: 0.10.5
- `--disable-extensions` didn't help
- no errors appear in the dev tools console
|
completed
|
ctrl+shift+j yields "Cannot read property 'openViewlet' of undefined" ## explanation
The default keyboard shortcuts file contains:
```
{
"key": "ctrl+shift+j",
"command": "workbench.action.search.toggleQueryDetails",
"when": "searchViewletVisible"
},
```
So, I tried it out, but got an error.
## repro
1. Open search view (via <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>f</kbd> or mouse click).
2. Attempt to use shortcut <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>j</kbd>.
3. See error message: "Cannot read property 'openViewlet' of undefined".
## supporting info
- version: 0.10.5
- `--disable-extensions` didn't help
- no errors appear in the dev tools console
| 243 |
[] |
0
|
False
|
|
1598
|
install extension is slow (needs caching?)
|
2015-12-23 01:07:15+00:00
|
2016-01-04 11:59:57+00:00
|
Invoking the command `ext install` repeatedly is really slow.
When you invoke the command, a little blue line scrolls horizontally to show it's doing something (fetching the extension database?), and eventually displays a list of extensions you can install. Repeatedly invoking the command should cache this work from last time, but it seems to re-fetch (or whatever it's doing) every time, which is fairly annoying when I want to install a few extensions at once.
|
completed
|
install extension is slow (needs caching?) Invoking the command `ext install` repeatedly is really slow.
When you invoke the command, a little blue line scrolls horizontally to show it's doing something (fetching the extension database?), and eventually displays a list of extensions you can install. Repeatedly invoking the command should cache this work from last time, but it seems to re-fetch (or whatever it's doing) every time, which is fairly annoying when I want to install a few extensions at once.
| 129 |
[] |
0
|
False
|
|
1594
|
[java] enum with values coloring is off
|
2015-12-22 23:24:27+00:00
|
2017-02-22 22:01:17+00:00
|
The coloring of java enums if off when you add values. The strings in the below example will be colored as if it's code (i.e. 'Banana', 'Apple', 'Co' and 'Nut' are blue; and 'co' is white
```
public enum Fuit {
Banana ("Banana"),
Apple ("Apple"),
Coconut ("Co co Nut");
public final String text;
private Option(final String text) {
this.text = text;
}
}
```
|
completed
|
[java] enum with values coloring is off The coloring of java enums if off when you add values. The strings in the below example will be colored as if it's code (i.e. 'Banana', 'Apple', 'Co' and 'Nut' are blue; and 'co' is white
```
public enum Fuit {
Banana ("Banana"),
Apple ("Apple"),
Coconut ("Co co Nut");
public final String text;
private Option(final String text) {
this.text = text;
}
}
```
| 129 |
[] |
0
|
False
|
|
1590
|
JSDoc Comment seen as code error in JavaScript
|
2015-12-22 21:46:13+00:00
|
2016-03-16 13:55:26+00:00
|
The JSDoc comment `* @param {Array<string>} [plugins=['defaults']] - plugins to enables` shows a red underline below the `<` before string.
When clicking on the error/warning notice, it says `'}' expected.`
It is expected that code within a comment does not give error/warning notices for JavaScript
Using version 0.10.5 on Windows 10.
|
completed
|
JSDoc Comment seen as code error in JavaScript The JSDoc comment `* @param {Array<string>} [plugins=['defaults']] - plugins to enables` shows a red underline below the `<` before string.
When clicking on the error/warning notice, it says `'}' expected.`
It is expected that code within a comment does not give error/warning notices for JavaScript
Using version 0.10.5 on Windows 10.
| 107 |
[] |
0
|
False
|
|
1588
|
'Find' silently fails after 1000 results
|
2015-12-22 20:07:16+00:00
|
2016-01-09 01:01:37+00:00
|
If you search for something, Code only finds the first 1000 instances - it silently fails to navigate and/or highlight further instances.
This makes viewing/searching log files (which often have 10Ks or more instances) pretty much a no-go with Code.
|
completed
|
'Find' silently fails after 1000 results If you search for something, Code only finds the first 1000 instances - it silently fails to navigate and/or highlight further instances.
This makes viewing/searching log files (which often have 10Ks or more instances) pretty much a no-go with Code.
| 130 |
[] |
0
|
False
|
|
1585
|
URL containing parentheses not properly detected in Java comment
|
2015-12-22 18:28:04+00:00
|
2016-02-22 12:30:23+00:00
|
If a URL such as http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx is included in a comment in a Java source file, Visual Studio Code won't properly detect where it ends, omitting the last six characters and resulting in a broken link.
|
completed
|
URL containing parentheses not properly detected in Java comment If a URL such as http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx is included in a comment in a Java source file, Visual Studio Code won't properly detect where it ends, omitting the last six characters and resulting in a broken link.
| 95 |
[] |
0
|
False
|
|
1584
|
Hovering over new watch expression input box crops the end of input
|
2015-12-22 18:25:11+00:00
|
2016-11-11 16:44:08+00:00
|
1. Create a new watch expression
2. While the input box is active hover over it, notice the end gets cropped
|
completed
|
Hovering over new watch expression input box crops the end of input 1. Create a new watch expression
2. While the input box is active hover over it, notice the end gets cropped
| 104 |
[] |
0
|
False
|
|
1583
|
[python] Disassociate .gn with python language
|
2015-12-22 17:49:28+00:00
|
2016-01-11 15:28:29+00:00
|
While Python worked well with GN in v0.10.3, since then the progress made with
the Python language syntax highlighting doesn't play well with the extra quirks
on top of Python that GN introduces (braces, no colons to indicate blocks).
Making it less usable than no language mode.
|
[python] Disassociate .gn with python language While Python worked well with GN in v0.10.3, since then the progress made with
the Python language syntax highlighting doesn't play well with the extra quirks
on top of Python that GN introduces (braces, no colons to indicate blocks).
Making it less usable than no language mode.
| 87 |
[] |
0
|
False
|
||
1581
|
Shift+tab from the "replace" textbox doesn't bring to to the "find" textbox
|
2015-12-22 17:05:33+00:00
|
2016-01-08 12:25:43+00:00
|
Actually, you cannot even reach that textbox using tab from the replace text box in a reasonable way, as I found out.
Repro steps:
- Open a text file
- Hit Ctrl+H
- Hit Tab
- Hit Shift+Tab (once, but also as much as you want)
|
completed
|
Shift+tab from the "replace" textbox doesn't bring to to the "find" textbox Actually, you cannot even reach that textbox using tab from the replace text box in a reasonable way, as I found out.
Repro steps:
- Open a text file
- Hit Ctrl+H
- Hit Tab
- Hit Shift+Tab (once, but also as much as you want)
| 88 |
[] |
0
|
False
|
|
1580
|
Changes in line endings are not correctly reflected in the extension host, leading to invalid offsets sent to external refactoring tools
|
2015-12-22 16:33:08+00:00
|
2016-01-13 16:32:13+00:00
|
See https://github.com/Microsoft/vscode-go/issues/165 for how this was discovered and how it effects the go extension, where I initially encountered the problem (reproduction instructions are available in [this comment](https://github.com/Microsoft/vscode-go/issues/165#issuecomment-166618653)).
In short: since the `gorename` tool seems to always convert the document's line endings to `LF`, running it once when the endings are initially `CRLF` may seem to work at first, but at the second time, (when the endings are changed to `LF`) since the extension host still calculates offsets based on `CRLF` the tool would give what seemed like 'strange' errors about invalid offsets that didn't seem to make sense at first. Changing line endings using the UI itself didn't seem to matter, but reopening the file 'magically' fixed it.
Tracing this into the vscode source: in `extHostDocuments.ts`, within the `BaseTextDocument` class it seems like the [`_eol` property](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L185) is not updated when the line endings change. This means that the [`offsetAt` function](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L185) may return invalid values. Fixing this might not be sufficient. In order to force the [`_ensureLineStarts` function](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L329) to recalculate the line offsets it seems that the [`_lineStarts` object](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L190) needs to be reset every time that the line endings change (this includes cases where they are changed by an external tool or editor). I would recommend this should also handle the case where only a _single_ (or some) line ending changes (meaning the line endings are inconsistent), as in some rare cases some external tools may modify the text in this way.
|
completed
|
Changes in line endings are not correctly reflected in the extension host, leading to invalid offsets sent to external refactoring tools See https://github.com/Microsoft/vscode-go/issues/165 for how this was discovered and how it effects the go extension, where I initially encountered the problem (reproduction instructions are available in [this comment](https://github.com/Microsoft/vscode-go/issues/165#issuecomment-166618653)).
In short: since the `gorename` tool seems to always convert the document's line endings to `LF`, running it once when the endings are initially `CRLF` may seem to work at first, but at the second time, (when the endings are changed to `LF`) since the extension host still calculates offsets based on `CRLF` the tool would give what seemed like 'strange' errors about invalid offsets that didn't seem to make sense at first. Changing line endings using the UI itself didn't seem to matter, but reopening the file 'magically' fixed it.
Tracing this into the vscode source: in `extHostDocuments.ts`, within the `BaseTextDocument` class it seems like the [`_eol` property](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L185) is not updated when the line endings change. This means that the [`offsetAt` function](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L185) may return invalid values. Fixing this might not be sufficient. In order to force the [`_ensureLineStarts` function](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L329) to recalculate the line offsets it seems that the [`_lineStarts` object](https://github.com/Microsoft/vscode/blob/70ee90dcc1c9a3094ae2ba94f8d0c210a72e499e/src/vs/workbench/api/common/extHostDocuments.ts#L190) needs to be reset every time that the line endings change (this includes cases where they are changed by an external tool or editor). I would recommend this should also handle the case where only a _single_ (or some) line ending changes (meaning the line endings are inconsistent), as in some rare cases some external tools may modify the text in this way.
| 735 |
[] |
0
|
False
|
|
1579
|
Sanity check file names before writing to disk
|
2015-12-22 15:32:04+00:00
|
2016-02-29 17:09:47+00:00
|
I just manged to save a file with the filename "cd.." because I wanted to go to the upper folder and mistakenly typed the "cd" as well instead of just ".." in the file save dialog. The file was in fact created but Windows is not too fond of that name. The file is pretty much unusable outside of VSCode.
After investigating further it looks like trailing dots are not getting removed when saving a file. Other programs either remove all the dots or add an extra file extension. VSCode doesn't and typos prove to be quite problematic that way :)
|
completed
|
Sanity check file names before writing to disk I just manged to save a file with the filename "cd.." because I wanted to go to the upper folder and mistakenly typed the "cd" as well instead of just ".." in the file save dialog. The file was in fact created but Windows is not too fond of that name. The file is pretty much unusable outside of VSCode.
After investigating further it looks like trailing dots are not getting removed when saving a file. Other programs either remove all the dots or add an extra file extension. VSCode doesn't and typos prove to be quite problematic that way :)
| 143 |
[] |
0
|
False
|
|
1578
|
No context menu in any input field
|
2015-12-22 15:26:12+00:00
|
2016-02-03 10:20:24+00:00
|
On OSX. I usually CTRL+C, CTRL+V; but this time I happened to right click and noticed it wouldn't work.
|
completed
|
No context menu in any input field On OSX. I usually CTRL+C, CTRL+V; but this time I happened to right click and noticed it wouldn't work.
| 42 |
[] |
0
|
False
|
|
1576
|
When I opened my solution, always got this error message.
|
2015-12-22 13:16:09+00:00
|
2016-01-20 09:30:59+00:00
|
When I opened my solution, always got this error message.I am from China.
My dev-environment:
> OS: Microsoft Windows 10
> IDE: Visual Studio Code 0.10.5
> DNX: 1.0.0-rc1-update1
**The solution created by visual studio 2013.**
---
*.csproj
�� Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)
�� Microsoft.Build.Evaluation.Project.Data.InitializeForEvaluation(IToolsetProvider toolsetProvider)
�� Microsoft.Build.Evaluation.Evaluator`4..ctor(IEvaluatorData`4 data, ProjectRootElement projectRootElement, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)
�� Microsoft.Build.Evaluation.Evaluator`4.Evaluate(IEvaluatorData`4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)
�� Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation)
�� Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)
�� Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
�� Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary`2 globalProperties, String toolsVersion)
�� OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Create(MSBuildOptions options, ILogger logger, String solutionDirectory, String projectFilePath, ICollection`1 diagnostics)
�� OmniSharp.MSBuild.MSBuildProjectSystem.CreateProject(String projectFilePath)
|
completed
|
When I opened my solution, always got this error message. When I opened my solution, always got this error message.I am from China.
My dev-environment:
> OS: Microsoft Windows 10
> IDE: Visual Studio Code 0.10.5
> DNX: 1.0.0-rc1-update1
**The solution created by visual studio 2013.**
---
*.csproj
�� Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject(String errorSubCategoryResourceName, IElementLocation elementLocation, String resourceName, Object[] args)
�� Microsoft.Build.Evaluation.Project.Data.InitializeForEvaluation(IToolsetProvider toolsetProvider)
�� Microsoft.Build.Evaluation.Evaluator`4..ctor(IEvaluatorData`4 data, ProjectRootElement projectRootElement, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)
�� Microsoft.Build.Evaluation.Evaluator`4.Evaluate(IEvaluatorData`4 data, ProjectRootElement root, ProjectLoadSettings loadSettings, Int32 maxNodeCount, PropertyDictionary`1 environmentProperties, ILoggingService loggingService, IItemFactory`2 itemFactory, IToolsetProvider toolsetProvider, ProjectRootElementCache projectRootElementCache, BuildEventContext buildEventContext, ProjectInstance projectInstanceIfAnyForDebuggerOnly)
�� Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary(ILoggingService loggingServiceForEvaluation)
�� Microsoft.Build.Evaluation.Project.Initialize(IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectLoadSettings loadSettings)
�� Microsoft.Build.Evaluation.Project..ctor(String projectFile, IDictionary`2 globalProperties, String toolsVersion, String subToolsetVersion, ProjectCollection projectCollection, ProjectLoadSettings loadSettings)
�� Microsoft.Build.Evaluation.ProjectCollection.LoadProject(String fileName, IDictionary`2 globalProperties, String toolsVersion)
�� OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Create(MSBuildOptions options, ILogger logger, String solutionDirectory, String projectFilePath, ICollection`1 diagnostics)
�� OmniSharp.MSBuild.MSBuildProjectSystem.CreateProject(String projectFilePath)
| 661 |
[] |
0
|
False
|
|
1575
|
dropped support for relative paths in launch.json: UX problems
|
2015-12-22 13:07:19+00:00
|
2016-01-12 16:13:09+00:00
|
When using old launch.jsons with relative paths, VSCode throws warnings into the users face.
I don't think that we can ship with this in January.
- the warning doesn't specify what attributes are affected, instead I see only the value that I will have to fix. Since the fix has already been applied to the value, it is difficult to locate the value in the lunch.json.
- "${workspaceRoot}/." (and variants) look a bit silly. This is just "${workspaceRoot}"
- Sometimes it is impossible to figure out what to do. This launch.json looks OK but VSCode still complains that there is a "." somewhere. I couldn't spot the error: .
In general I think that we should not show warnings in this way because it is annoying and unhelpful. Instead we should show warning (later "error") squigglies in the json editor and offer intellisense to help the user inserting the missing "${workspaceRoot}" and have a "light bulb" action for fixing the whole launch json (as an example use the validation that got introduced for the Keyboard Shortcuts json).
If this is not possible for January, I suggest that we only fix our intellisense, templates, samples, etc. but show no warnings in the launch.json editor.
|
completed
|
dropped support for relative paths in launch.json: UX problems When using old launch.jsons with relative paths, VSCode throws warnings into the users face.
I don't think that we can ship with this in January.
- the warning doesn't specify what attributes are affected, instead I see only the value that I will have to fix. Since the fix has already been applied to the value, it is difficult to locate the value in the lunch.json.
- "${workspaceRoot}/." (and variants) look a bit silly. This is just "${workspaceRoot}"
- Sometimes it is impossible to figure out what to do. This launch.json looks OK but VSCode still complains that there is a "." somewhere. I couldn't spot the error: .
In general I think that we should not show warnings in this way because it is annoying and unhelpful. Instead we should show warning (later "error") squigglies in the json editor and offer intellisense to help the user inserting the missing "${workspaceRoot}" and have a "light bulb" action for fixing the whole launch json (as an example use the validation that got introduced for the Keyboard Shortcuts json).
If this is not possible for January, I suggest that we only fix our intellisense, templates, samples, etc. but show no warnings in the launch.json editor.
| 444 |
[] |
0
|
False
|
|
1568
|
Debugger adapter's "runtimeArgs" parameter is ignored
|
2015-12-22 08:30:56+00:00
|
2015-12-22 09:00:30+00:00
|
I am trying to use native ES6 features like `Promise` and `Map` in my debug adapter. To enable these features, I've created this configuration for my debugger extension:
```
...
"contributes": {
"debuggers": [
{
"program": "./out/DebugSession.js",
"runtime": "node",
"runtimeArgs": ["--harmony"],
...
```
However the `--harmony` parameter never seems to make it to the command line of the launched code subprocess, so it fails upon encountering ES6 features in the code.
|
completed
|
Debugger adapter's "runtimeArgs" parameter is ignored I am trying to use native ES6 features like `Promise` and `Map` in my debug adapter. To enable these features, I've created this configuration for my debugger extension:
```
...
"contributes": {
"debuggers": [
{
"program": "./out/DebugSession.js",
"runtime": "node",
"runtimeArgs": ["--harmony"],
...
```
However the `--harmony` parameter never seems to make it to the command line of the launched code subprocess, so it fails upon encountering ES6 features in the code.
| 168 |
[] |
0
|
False
|
|
1562
|
QuickFix Generate a class for 'class name' in 'namespace' (in a new file) doesn't work
|
2015-12-22 03:36:16+00:00
|
2016-01-20 09:28:07+00:00
|
no files get created and omnisharp needs restart to function.
here is omnisharp log.
[INFO] Starting OmniSharp at 'd:\c\Work\vscodeunity\vscodeunity-csharp.sln'...
[INFO] Started OmniSharp from 'c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\jrieken.vscode-omnisharp\bin\omnisharp.cmd' with process id 2768...
[INFORMATION:OmniSharp.Startup] Omnisharp server running using stdio at location 'd:\c\Work\vscodeunity' on host 7196.
[INFORMATION:OmniSharp.Dnx.DnxPaths] Using runtime 'C:\Users\Taraweesh.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1'.
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Scanning 'd:\c\Work\vscodeunity' for DNX projects
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] No project.json based projects found
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Detecting projects in 'd:\c\Work\vscodeunity\vscodeunity-csharp.sln'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Using toolset 2.0 for d:\c\Work\vscodeunity\Assembly-CSharp-vs.csproj
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Loading project from 'd:\c\Work\vscodeunity\Assembly-CSharp-vs.csproj'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Loading project from 'd:\c\Work\vscodeunity\Assembly-CSharp-Editor-vs.csproj'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Using toolset 2.0 for d:\c\Work\vscodeunity\Assembly-CSharp-Editor-vs.csproj
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Detecting CSX files in 'd:\c\Work\vscodeunity'.
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Could not find any CSX files
[INFORMATION:OmniSharp.Startup] Solution has finished loading
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/getcodeactions: 200 1114ms
[INFORMATION:OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.RunCodeActionService] Applying Microsoft.CodeAnalysis.GenerateType.AbstractGenerateTypeService`6+GenerateTypeCodeAction[Microsoft.CodeAnalysis.CSharp.GenerateType.CSharpGenerateTypeService,Microsoft.CodeAnalysis.CSharp.Syntax.SimpleNameSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ObjectCreationExpressionSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ExpressionSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.TypeDeclarationSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ArgumentSyntax]
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 522ms
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 8ms
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 4ms
|
completed
|
QuickFix Generate a class for 'class name' in 'namespace' (in a new file) doesn't work no files get created and omnisharp needs restart to function.
here is omnisharp log.
[INFO] Starting OmniSharp at 'd:\c\Work\vscodeunity\vscodeunity-csharp.sln'...
[INFO] Started OmniSharp from 'c:\Program Files (x86)\Microsoft VS Code\resources\app\extensions\jrieken.vscode-omnisharp\bin\omnisharp.cmd' with process id 2768...
[INFORMATION:OmniSharp.Startup] Omnisharp server running using stdio at location 'd:\c\Work\vscodeunity' on host 7196.
[INFORMATION:OmniSharp.Dnx.DnxPaths] Using runtime 'C:\Users\Taraweesh.dnx\runtimes\dnx-clr-win-x86.1.0.0-rc1-update1'.
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Scanning 'd:\c\Work\vscodeunity' for DNX projects
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] No project.json based projects found
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Detecting projects in 'd:\c\Work\vscodeunity\vscodeunity-csharp.sln'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Using toolset 2.0 for d:\c\Work\vscodeunity\Assembly-CSharp-vs.csproj
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Loading project from 'd:\c\Work\vscodeunity\Assembly-CSharp-vs.csproj'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Loading project from 'd:\c\Work\vscodeunity\Assembly-CSharp-Editor-vs.csproj'.
[INFORMATION:OmniSharp.MSBuild.MSBuildProjectSystem] Using toolset 2.0 for d:\c\Work\vscodeunity\Assembly-CSharp-Editor-vs.csproj
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Detecting CSX files in 'd:\c\Work\vscodeunity'.
[INFORMATION:OmniSharp.ScriptCs.ScriptCsProjectSystem] Could not find any CSX files
[INFORMATION:OmniSharp.Startup] Solution has finished loading
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/getcodeactions: 200 1114ms
[INFORMATION:OmniSharp.Roslyn.CSharp.Services.Refactoring.V2.RunCodeActionService] Applying Microsoft.CodeAnalysis.GenerateType.AbstractGenerateTypeService`6+GenerateTypeCodeAction[Microsoft.CodeAnalysis.CSharp.GenerateType.CSharpGenerateTypeService,Microsoft.CodeAnalysis.CSharp.Syntax.SimpleNameSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ObjectCreationExpressionSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ExpressionSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.TypeDeclarationSyntax,Microsoft.CodeAnalysis.CSharp.Syntax.ArgumentSyntax]
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 522ms
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 8ms
[INFORMATION:OmniSharp.Middleware.LoggingMiddleware] /v2/runcodeaction: 200 4ms
| 970 |
[] |
0
|
False
|
|
1559
|
[jade] Syntax Highlighting Stops Working on Unbuffered Code
|
2015-12-21 23:48:45+00:00
|
2017-02-07 10:20:02+00:00
|
As soon as I use unbuffered code, the syntax highlighting stops working.
In the attached, `.row.source-of-income-row` has lost syntax highlighting -- and the rest of the jade file too.
|
completed
|
[jade] Syntax Highlighting Stops Working on Unbuffered Code As soon as I use unbuffered code, the syntax highlighting stops working.
In the attached, `.row.source-of-income-row` has lost syntax highlighting -- and the rest of the jade file too.
| 130 |
[] |
0
|
False
|
|
1558
|
"Electron" appears as Github login popup has no title
|
2015-12-21 23:45:29+00:00
|
2016-01-05 10:02:33+00:00
|
|
completed
|
"Electron" appears as Github login popup has no title 
| 84 |
[] |
0
|
False
|
|
1550
|
[yaml] keys with hyphens break syntax highlighting
|
2015-12-21 18:48:15+00:00
|
2016-09-15 19:52:47+00:00
|
Editing a yaml file which has a hyphen in an unquoted key name seems to break syntax highlighting for the value of that key
Tested in 0.10.5
|
completed
|
[yaml] keys with hyphens break syntax highlighting 
Editing a yaml file which has a hyphen in an unquoted key name seems to break syntax highlighting for the value of that key
Tested in 0.10.5
| 110 |
[] |
0
|
False
|
|
1549
|
Localized keybindings mismatched
|
2015-12-21 17:14:50+00:00
|
2017-03-24 16:50:30+00:00
|
The "navigateBack" command is listed in my config file as:
```
{ "key": "ctrl+alt+-", "command": "workbench.action.navigateBack" }
```
I am using the German keyboard layout with Visual Studio Code. I get a tooltip over "ctrl+alt+-" telling me to press "ctrl+alt+ß" instead (the ß key of the German keyboard is at the position of the - key on the English keyboard)
However, the command I actually have to press in order to navigate backwards is ctrl+alt+-, using the - key of the German keyboard, which is somewhere else entirely.
Thus, the tooltip is incorrect while the key as it is stated in the config file is correct.
Edit: my operating system is Linux x64 (Ubuntu 14.04)
|
completed
|
Localized keybindings mismatched The "navigateBack" command is listed in my config file as:
```
{ "key": "ctrl+alt+-", "command": "workbench.action.navigateBack" }
```
I am using the German keyboard layout with Visual Studio Code. I get a tooltip over "ctrl+alt+-" telling me to press "ctrl+alt+ß" instead (the ß key of the German keyboard is at the position of the - key on the English keyboard)
However, the command I actually have to press in order to navigate backwards is ctrl+alt+-, using the - key of the German keyboard, which is somewhere else entirely.
Thus, the tooltip is incorrect while the key as it is stated in the config file is correct.
Edit: my operating system is Linux x64 (Ubuntu 14.04)
| 203 |
[] |
0
|
False
|
|
1545
|
When using multiple carets, autocomplete only completes the first one selected
|
2015-12-21 15:43:41+00:00
|
2017-04-05 12:40:58+00:00
|
An image says more than a thousand words:
|
completed
|
When using multiple carets, autocomplete only completes the first one selected An image says more than a thousand words:
| 92 |
[] |
0
|
False
|
|
1544
|
Git keyboard navigation bug
|
2015-12-21 15:28:43+00:00
|
2016-01-04 11:53:20+00:00
|
**Repro**
- Make changes
- Open Git view
- Highlight first file in file view
- Press down then enter on keyboard
**Expected**
- Shows next file
**Actual**
- Highlights next file, but still shows first file
|
completed
|
Git keyboard navigation bug **Repro**
- Make changes
- Open Git view
- Highlight first file in file view
- Press down then enter on keyboard
**Expected**
- Shows next file
**Actual**
- Highlights next file, but still shows first file
| 58 |
[] |
0
|
False
|
|
1539
|
Git changes don't load anymore since latest update
|
2015-12-21 14:05:06+00:00
|
2016-01-04 15:14:02+00:00
|
Since the latest update I can't see any changes in my Git repositories.
I can see the amount of changed files in the repository indicated by the number below the git icon in the navigation bar. I can also see the changed files listed when I click on the icon. But when I want to see the changes then it never finishes loading.
The Git ouptut shows nothing special:
```
git fetch
git show HEAD:Source/AFile.txt
git show HEAD:Source/AFile.txt
```
Once I saw this error on the command line. I think it was related to this problem:
```
Uncaught Exception: TypeError: Unknown encoding: windows1252
TypeError: Unknown encoding: windows1252
at Buffer.slowToString (buffer.js:363:17)
at Buffer.toString (buffer.js:375:31)
at Socket.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\parts\git\electron-browser\gitApp.js:6:24085)
at Socket.g (events.js:260:16)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
Uncaught Exception: TypeError: Unknown encoding: windows1252
TypeError: Unknown encoding: windows1252
at Buffer.slowToString (buffer.js:363:17)
at Buffer.toString (buffer.js:375:31)
at Socket.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\parts\git\electron-browser\gitApp.js:6:24085)
at Socket.g (events.js:260:16)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
```
I'm running on Windows 10 with the latest updates. Having Git 2.6.4 (64 Bit) installed via Chocolatey. I'm on a german system and my files are usually encoded in Windows1252. But even changes on UTF8 encoded files can't be displayed in Visual Studio Code.
|
completed
|
Git changes don't load anymore since latest update Since the latest update I can't see any changes in my Git repositories.
I can see the amount of changed files in the repository indicated by the number below the git icon in the navigation bar. I can also see the changed files listed when I click on the icon. But when I want to see the changes then it never finishes loading.
The Git ouptut shows nothing special:
```
git fetch
git show HEAD:Source/AFile.txt
git show HEAD:Source/AFile.txt
```
Once I saw this error on the command line. I think it was related to this problem:
```
Uncaught Exception: TypeError: Unknown encoding: windows1252
TypeError: Unknown encoding: windows1252
at Buffer.slowToString (buffer.js:363:17)
at Buffer.toString (buffer.js:375:31)
at Socket.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\parts\git\electron-browser\gitApp.js:6:24085)
at Socket.g (events.js:260:16)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
Uncaught Exception: TypeError: Unknown encoding: windows1252
TypeError: Unknown encoding: windows1252
at Buffer.slowToString (buffer.js:363:17)
at Buffer.toString (buffer.js:375:31)
at Socket.<anonymous> (c:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\parts\git\electron-browser\gitApp.js:6:24085)
at Socket.g (events.js:260:16)
at emitOne (events.js:82:20)
at Socket.emit (events.js:169:7)
at Pipe._onclose (net.js:469:12)
```
I'm running on Windows 10 with the latest updates. Having Git 2.6.4 (64 Bit) installed via Chocolatey. I'm on a german system and my files are usually encoded in Windows1252. But even changes on UTF8 encoded files can't be displayed in Visual Studio Code.
| 582 |
[] |
0
|
False
|
|
1537
|
Markdown: HTML Coloring regression?
|
2015-12-21 13:13:16+00:00
|
2016-01-29 13:26:57+00:00
|
<img width="473" alt="screen shot 2015-12-21 at 14 12 57" src="https://cloud.githubusercontent.com/assets/900690/11931410/f8f583bc-a7ec-11e5-87fb-5f17874d9e2e.png">
|
completed
|
Markdown: HTML Coloring regression? <img width="473" alt="screen shot 2015-12-21 at 14 12 57" src="https://cloud.githubusercontent.com/assets/900690/11931410/f8f583bc-a7ec-11e5-87fb-5f17874d9e2e.png">
| 85 |
[] |
0
|
False
|
|
1536
|
modify launch.json Zoom back to 100%
|
2015-12-21 12:51:43+00:00
|
2015-12-22 10:54:18+00:00
|
When I modified launch.json, windows Zoom back to 100%.
|
completed
|
modify launch.json Zoom back to 100% When I modified launch.json, windows Zoom back to 100%.
| 28 |
[] |
0
|
False
|
|
1519
|
ES6. double letter with detect methods or var.
|
2015-12-21 07:12:13+00:00
|
2016-01-04 09:45:15+00:00
|
all version vs code have bug with ES6 + Russian language
then press tab or click
and we have ккомпонент in place компонент - double кк, first letter.
|
completed
|
ES6. double letter with detect methods or var. all version vs code have bug with ES6 + Russian language
then press tab or click
and we have ккомпонент in place компонент - double кк, first letter.
| 148 |
[] |
0
|
False
|
|
1514
|
Pass full "Source" object to "setBrealpointsRequest"
|
2015-12-21 00:39:19+00:00
|
2015-12-22 08:30:58+00:00
|
In order to support breakpoints in inlined source maps, it is necessary that the "Source" object passed to the "setBrealpointsRequest" contains the same attributes that are returned from the "stackTraceRequest" (Setting breakpoints in inlined source maps is similar to setting breakpoints in internal modules). Currently only the "name" attribute is passed, but not the "sourceReference" attribute. Without the "sourceReference" attribute it is difficult for the backend to identify the correct inlined source.
I suggest that you pass the source object returned from stackTraceRequest unmodified to setBrealpointsRequest. Ideally even with attributes that are not specified in the debug protocol spec.
|
completed
|
Pass full "Source" object to "setBrealpointsRequest" In order to support breakpoints in inlined source maps, it is necessary that the "Source" object passed to the "setBrealpointsRequest" contains the same attributes that are returned from the "stackTraceRequest" (Setting breakpoints in inlined source maps is similar to setting breakpoints in internal modules). Currently only the "name" attribute is passed, but not the "sourceReference" attribute. Without the "sourceReference" attribute it is difficult for the backend to identify the correct inlined source.
I suggest that you pass the source object returned from stackTraceRequest unmodified to setBrealpointsRequest. Ideally even with attributes that are not specified in the debug protocol spec.
| 194 |
[] |
0
|
False
|
|
1509
|
C# intellisense broken in constructors (0.10.5)
|
2015-12-20 17:14:09+00:00
|
2016-01-20 09:29:16+00:00
|
For regular C# functions, intellisense works as expected:
However, no intellisense shows up for constructors:
|
completed
|
C# intellisense broken in constructors (0.10.5) For regular C# functions, intellisense works as expected:
However, no intellisense shows up for constructors:
| 155 |
[] |
0
|
False
|
|
1508
|
Failed to execute git - I don't use git!
|
2015-12-20 14:32:13+00:00
|
2016-01-07 16:59:45+00:00
|
Why does my Visual Studio Code keep popping up this message?
<img width="181" alt="image" src="https://cloud.githubusercontent.com/assets/1559447/11918376/852a9170-a6fc-11e5-87cf-e7a8992da381.png">
I don't even use Git, and it started happening. Is it because I opened the Git panel?
Restarting does nothing, changing the settings/config doesn't help either. Super annoying and frustrated, please help. Thanks!
|
completed
|
Failed to execute git - I don't use git! Why does my Visual Studio Code keep popping up this message?
<img width="181" alt="image" src="https://cloud.githubusercontent.com/assets/1559447/11918376/852a9170-a6fc-11e5-87cf-e7a8992da381.png">
I don't even use Git, and it started happening. Is it because I opened the Git panel?
Restarting does nothing, changing the settings/config doesn't help either. Super annoying and frustrated, please help. Thanks!
| 145 |
[] |
0
|
False
|
|
1505
|
[css] Wrong CSS-Error with @supports rule
|
2015-12-20 12:15:15+00:00
|
2017-09-07 09:53:11+00:00
|
I get a CSS-eror using the supports-rule. I've used it in combination with the backdrop-filter property but it's not working with other properties neither.
<img width="607" alt="bildschirmfoto 2015-12-20 um 13 12 53" src="https://cloud.githubusercontent.com/assets/3930150/11917940/067916ba-a71c-11e5-8d57-d05691659ff1.png">
<img width="385" alt="bildschirmfoto 2015-12-20 um 13 13 10" src="https://cloud.githubusercontent.com/assets/3930150/11917939/06787a66-a71c-11e5-8517-e6c0088b7a4b.png">
|
completed
|
[css] Wrong CSS-Error with @supports rule I get a CSS-eror using the supports-rule. I've used it in combination with the backdrop-filter property but it's not working with other properties neither.
<img width="607" alt="bildschirmfoto 2015-12-20 um 13 12 53" src="https://cloud.githubusercontent.com/assets/3930150/11917940/067916ba-a71c-11e5-8d57-d05691659ff1.png">
<img width="385" alt="bildschirmfoto 2015-12-20 um 13 13 10" src="https://cloud.githubusercontent.com/assets/3930150/11917939/06787a66-a71c-11e5-8517-e6c0088b7a4b.png">
| 199 |
[] |
0
|
False
|
|
1504
|
[theme] Monokai theme: parameters are not colored in Orange
|
2015-12-20 11:18:48+00:00
|
2016-01-13 14:00:13+00:00
|
Extracted from issue #1470.
I am using Monokai, where function parameters are displayed in orange, but with this update the parameters are displayed in gray although the Monokai.tmTheme clearly states that parameters should be orange (#FD971F).
|
completed
|
[theme] Monokai theme: parameters are not colored in Orange Extracted from issue #1470.
I am using Monokai, where function parameters are displayed in orange, but with this update the parameters are displayed in gray although the Monokai.tmTheme clearly states that parameters should be orange (#FD971F).
| 82 |
[] |
0
|
False
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.