I just installed this and have no idea how to use. Is there directions somewhere?

def dot_on_n_dimensional_cube(n: int) -> list:
    '''docstring here''' 
    pass

breaks the docstring highlighting and highlighting below in predawn theme

1. Write some text in the editor.
2. Using the sidebar search (Ctrl + shift + F) search for your text.
3. Select it from the results pane.
4. Select/highlight a subset of your text.

Expected behaviour:
The highlighted text background would be noticeably different from the search match

Actual behaviour:
The highlighted background is exactly the same as the search match background resulting in your selected text being indistinguishable from the surrounding text leading to confusion around if and what is selected.

See here.
As title. Right now they appear to be JS.

Token inspector sees ) as )· and it's impossible to match it in the syntax file to give it a scope and a color.......
see how ) are not colorized because for some reason they are ) plus middle dot, instead of just ), matching it like \)· \)\· or event \).* doesn't work...

JavaScript and TypeScript seem to work fine.
Only color theme installed is: Tomorrow and Tomorrow Night Theme Kit

VS Code 1.8.1

Right now comment texts in PHP files are displayed either in white or in a light grey. They should be the same color as the // or /* slashes before them in order not to get confused with regular text, thus making the code easier to read.

I downloaded VSC Markdown Theme Kit, but I didn't kown how to make it work. Maybe giving a guide in README.md is more clear.

Hopefully this is the right spot to post this. If not maybe you could help me find the right spot?

Hello, I'm a VSCode theme creator (this one) and I think I've stumbled across a config that doesn't make sense:

The constructor function is using the "storage.type" textmate scope as it's highest priority scope. That scope, as far as I know, is for themeing keywords like const, let, etc. Why would you want your "constructor" keyword to be themed the same way? In my theme I have class methods and properties names themed and I want constructor to match. However because I also want const and let keywords themed, right now I can't get constructor to match class methods and properties.

[Enhancement]There's a very subtle color difference between JSON Keys and Booleans or Numbers but no difference between Key and Value when both are Strings. This makes large JSON files with all string data hard to navigate.

1337:

Dark(Visual Studio)

MarkMichos/1337-Scheme#7

From @vsccarl on March 17, 2016 19:0

• VSCode Version: 0.10.12-alpha
• OS Version: Windows 10

Steps to Reproduce:

1. Install Predawn theme
2. Change theme to Predawn Markdown

Actual: All text is red for any language type

Expected: Not entirely sure, but I would expect there to be some color differences. There is no documentation I could find on what to expect with this theme.

Copied from original issue: microsoft/vscode#4380

As vscode v1.12.0 is released, could you please have an update on the material theme.

Originally filed at microsoft/vscode#13271 by @bbarry

• VSCode Version: 1.5.2
• OS Version: Win7

Steps to Reproduce:

1. open xml file or ascx file or xsl file
2. open html or aspx file
3. switch to Red theme
4. compare open files

(file contents don't matter so long as there is some sort of xml document including tags, attributes and text content; it seems sufficient to save the same file with various extensions)

Expected Results:

• syntactic elements shared between these file types appear the same colors as they do in other themes (Dark theme for example)

Actual Results:

• xml and ascx files do not appear to identify much syntax compared to html or aspx files

It's currently not possible for non-insiders to fix issues like this microsoft/vscode#2158

[Enhancement]There's a very subtle color difference between JSON Keys and Booleans or Numbers but no difference between Key and Value when both are Strings. This makes large JSON files with all string data hard to navigate.

1337:

Dark(Visual Studio)

With Markdown Editor Dark theme in vscode, it is impossible to see those erroneous codes / text in json files. The text foreground color code is simply too hard to see from dark background.

I think the code section from the theme is located at

		{
			"name": "Invalid - Illegal",
			"scope": "invalid.illegal",
			"settings": {
				"background": "#06cdcd",
				"fontStyle": "",
				"foreground": "#060d31"
			}
		},

Thank you.

code is the same color as comments. It is often very difficult to distinguish between the two.
would you fix it? thx

This is barely readable:

Without a screenshot, users need to either view the theme on another editor or install it to check.

Allow the user to add a setting to automatically switch between dark and light themes depending on the system color-scheme

It's much easier to determine whether you like the theme if you see a piece of code being highlighted with it.

Would love to see a port of Palenight theme
https://github.com/equinusocio/material-theme/blob/develop/Material-Theme-Palenight.sublime-theme

refs material-theme/vsc-material-theme#565

I noticed that Microsoft licensed all of the included themes under The MIT License. I'm not sure if this is always appropriate, since none of the themes are the work of Microsoft.

• Predawn, Material and Tomorrow are released under The MIT License, so it's my understanding the original authors –Jamie Wilson, Mattias Astorino and Chris Kempson– should remain in the license.
• 3024 is my own theme and was released under the Public Domain Mark. I'm not sure if that allows re-releasing it under a different license. It's my work and I don't care that much, but it's about the details.
• 1337 does not specify any license, which to my understanding means “All Rights Reserved”. I don't think it can be released under a licensed the author hasn't approved of.

I understand that this confusion is likely caused by taking the themes from the Colorsublime repository, so it's probably their fault. Yet, that doesn't make it right.

Hi everybody.

I am using this great theme but there is a bug I've found:

• it doesn't properly highlight/detect the arguments of global functions.

They end up the same color as the function name.

Developers, is there any chance to update this theme kit? Thak you very much.

From @jrajav on January 21, 2016 20:48

I'm not sure if this is an issue with Vscode or with the Tomorrow color theme itself, but there's no repo or issue tracker listed anywhere for the extension, so...

The light version in this color theme:

https://marketplace.visualstudio.com/items/ms-vscode.Theme-TomorrowKit

Results in some code elements being white on the white background:

In this case, the commas and colons in this JSON file.

Copied from original issue: microsoft/vscode#2158

There are important files that Microsoft projects should all have that are not present in this repository. A pull request has been opened to add the missing file(s). When the pr is merged this issue will be closed automatically.

Microsoft teams can learn more about this effort and share feedback within the open source guidance available internally.

Merge this pull request

See http://chriskempson.github.io/base16/#tomorrow

A VSCode template could be added to the base16-builder while doing this.

The background color for the characters && in line 40 is almost invisible as it is coloured light yellow.

Please find the attachment. The issue exists even in darker theme.

Line focused

Line not focused

Mac OS: Mojave 10.14.6
VS Version: 1.38.1

After update to vscode 1.7.1
3024 cannot highlight javascript class.

Reproduce:

1. Create a diff file. Use git show > foo.diff, or eg. copy the following to a new diff file:

diff --git a/.travis.yml b/.travis.yml
index ef975079..4585f88e 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -8,13 +8,13 @@ addons:
   postgresql: "9.4"
 
 env:
-  - TOXENV=py27-django110
-  - TOXENV=py27-django111
-  - TOXENV=py34-django110
-  - TOXENV=py34-django111
-  - TOXENV=py35-django110
-  - TOXENV=py35-django111
-  - TOXENV=py36-django111
+  - TOXENV=py27-django110-jsonfield,py27-django110-bjson
+  - TOXENV=py27-django111-jsonfield,py27-django110-bjson
+  - TOXENV=py34-django110-jsonfield,py27-django110-bjson
+  - TOXENV=py34-django111-jsonfield,py27-django110-bjson
+  - TOXENV=py35-django110-jsonfield,py27-django110-bjson
+  - TOXENV=py35-django111-jsonfield,py27-django110-bjson
+  - TOXENV=py36-django111-jsonfield,py27-django110-bjson
   - TOXENV=flake8

The file will not be highlighted in the following color themes:

• Tomorrow
• Tomorrow Night
• Tomorrow Night Bright
• Tomorrow Night Eighties

The file is correctly highlighted in Tomorrow Night Blue.

It's confusing having the names differ from on the marketplace to in-editor.

• Material Darker -> Material Night Eighties
• Material Lighter -> Material Night

The top line in the attached image is the correct color for quoted text in this context. I want to format with line breaks for readability, but the color change makes things less readable. I have reviewed the Inspect Editor Tokens and Scopes and the main difference between the first two paths is that "standard token type" is "String" for the first path and "Other" for the second path. The "textmate scopes" are different, but very similar, both starting with string.quoted.double.html.
The "foreground" for the first path is:
string { "foreground": "#BC670F", "background": "#FBE9AD1A", "fontStyle": "" }
For the second path it's:
meta.tag string.quoted { "foreground": "#6D98CF" }
The third path is included in the image to illustrate the possibility that VSCode thinks that the line break means that the SVG element is not properly terminated, even though it is.

See https://stackoverflow.com/questions/76148772/visual-studio-code-line-break-in-svg-element-declaration-changes-literal-text

I wanted to attach a .html file example here, but it only accepts image files. It's a small file so I'll drop it right here:

<html>
  <head>
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">
  </head>
  <body>
    <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 100 100">
      <path id="oneLine" d="M1,1 L2,2"/>
      <path id="twoLines"
            d="M1,1 L2,2"/>
    </svg>
  </body>
</html>

original code is:

@media screen and (device-aspect-ratio: 40/71) {
    blah{...}
}