vscode

I'm making a client-side code editor with rudimentary Git support, and syntax highlighting for diff/patch files would be really nice - a way to view the whole diff in a single window (alternative to existing diffeditor - with similar colors to git diff console coloring), maybe would be useful for others too.

https://github.com/microsoft/monaco-languages/ asks to create issues in this repo...

• Foam version: 0.13.1
• Platform: Linux
• Issue occur on the foam template repo: Yes

Summary
Ignoring files requires a restart of VS Code for the setting to be applied.

Steps to reproduce

1. Add a folder to the foam.files.ignore setting. E.g. "foam.files.ignore": ["/docs/**/*"]
2. Look at graph with "Show Graph" and see that t

Describe the bug
The property 'editor' can be undefined (see Screenshots section).

To Reproduce
Steps to reproduce the behavior:

1. Start VSCode
2. Check Breakpoints > Promise Rejects and Breakpoints > Uncaught Exceptions
3. Start my extension in debug mode (Debugger > Launch client). I believe, that can be r

🚀 Feature Proposal

Adding leading zero in the question number will be an awesome feature for file explorer to sort files by the name.

now defaultFormatterOptions.prettier global config position is only support a .prettierrc in home directory.
but prettier ext have options prettier.configPath to custom global config file directory.

defaultFormatterOptions.prettier can support 'prettier.configPath' ?

https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode
#Configuring Default Options

how to use gui in the AidLearning?how to custom the gui?

• I'm sure this issue is not a duplicate.

• I'm submitting an icon request:

  • Type: file_type
  • Icon Name: ``
  • Sample original Icon: ![logo](https://upload.wikimedia.org/wikipedia/commons/7/7e/

The app already includes a manifest.json - but it's lacking some details. Most notably:

• It has no Service Worker included, so Chrome etc. says "no"
• the app lacks any proper icons (although this also applies to favicons) - maybe some should be added :)

I would like to request a little more distinction in the syntax highlighting for css variables.