macOS 10.13.1
VSCode Insiders 1.19
npm version 5.3.0

When I hit F5 with index.ts loaded, I get an error message as shown

Like:
&
<
>

You probably know it:

func[0];
`text ${func[0]} text`;

Suggestion

Change the terminal panel background to be slightly different than the sideBar. I changed the color to match the background as the the activityBar.

// theme-extend: sapphire (dim)
"workbench.colorCustomizations": {
  "panel.background": "#0b121c"
}

Preview

Thought I would throw this suggestion out there before I made my own theme extension.

The global settings weren't kept in sync, is this interface needed anymore?

Currently tmTheme global settings very specific to vscode are in the generic interface.

Coming in v1.25, should be the primary accent color.

It's too much effort to do a detailed write up if you publish multiple themes, maybe the generator could generate one, including images to demonstrate the colors?

Why not Python

Added in microsoft/vscode#19735

eg. Setting the panel background like this:

colorSet = {
  base: { ... },
  overrides: {
    "terminal.background": "..."
  }
}

function fun(){}
let fun = () => 0;

class Cla {
    meth() {}
    meth = () => 0;
    meth = function() {}
}

Generated result:

All of my installed themes use them consistently:

Example JS:

let str = 'text \n \t \\ text'

I tried not to open an issue for this particular request, but I can't contact @Tyriar directly through github or via email address or any other private comunication channel... so only for this time I wil do this.
you have posted an image of the vscode window and I was wonder if you could tell me what is the font you where using in the code editor. I have tried to get it in most common font websites but i can't find it. This is the image you have posted:

sorry for the inconvenient I may caused.

A table that shows what languages are supported by what programs.

I very like you theme,but I don't know what font you use?can you tell me?

microsoft/vscode#26093

In JS/TS represented by ${}:

let str = `text${text}text` 

A theme generator is a great idea! I'd like to take it further and offer a web interface for the theme generator. But a 100% accurate preview would be essential to make such a web interface really useful. My first thought was to simply use the standalone Monaco editor for the previews, but unfortunately I found out that Monaco doesn't support TextMate grammars (as described in the Monaco FAQ) Only hope seems to be WebAssembly, but I don't think it will gain that much traction anytime soon.

So my conclusion is it won't be possible to do at the moment. But maybe you have an idea how a proper preview could be implemented, outside the context of VS Code?

From the docs:

Make your changes to the colors in index.ts and hit F5 to build the theme and launch the a new VS Code window with your theme available in the command palette (ctrl/cmd+shift+p > "Color Theme").

Made my changes, hit f5. Nothing happened. Ran the build task via the tasks panel. Theme was built, but a new VSC window was never opened.

OSX, VSC v1.12.0

eg.

        <dict>
            <key>name</key>
            <string>Constant</string>
            <key>scope</key>
            <string>constant</string>
            <key>settings</key>
            <dict>
                <key>foreground</key>
                <string>#ffe792</string>
                <key>fontStyle</key>
                <string></string>
            </dict>
        </dict>

Should these be their own thing or should they be bundled?

Is this one of the uses they are adding the bundling support for?

eg. storage is a type of keyword

Currently vscode text styles are hard-coded for each color type.

Upstream issue: microsoft/vscode#19647

Some open questions:

• Should color1, color2, etc. be named accent1, accent2 or something more specific?
• How do we mitigate heaps of language specific syntax color types such as markdownQuote, cssTag, etc.

For example class could fallback to keyword, meaning if class was not specified it would use keyword's color. This would allow themes to only specify a subset of colors but be fairly complete.

There is a downside to this in that it would make it harder to not set certain scopes if that is desired?

Right now background fallback colors are very rough based on a quick run through of the Dark+ theme. Maybe we can improve upon it?

The fallbacks we land on may eventually be upstreamed to VS Code.

Related: #22

Also want to target terminals. Should terminal theming be a separate module instead? Is theme generator too generic?

Sorry for asking this irrelative question.
I'm dying to know where does the mini code map on the right side just like Sublime come from.
What's the name of the extension?

Currently themes are generated using editor.lineHighlightBorder with no option for setting the background.

Check declares, interfaces, etc

Needs to support:

• setting of output file
• passing in a js/json file with the colorset(s)
• specifying which program theme is being generated

Default should be primary accent color with some transparency.

Example:

Text `code` text

Consumers can only find the true capabilities of the generator by looking through examples or searching the interface. The bigger parts like syntax, terminal, background fallbacks etc. should be called out on the readme.