Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

Please confirm that the issue/resolution isn't already documented

• [ X ] I checked the Docs page and my issue is not mentioned there.

To Reproduce
Steps to reproduc

• Foam version: 0.9.1
• Platform: Mac
• Issue occur on the foam template repo: Yes

Summary
Having a folder named with a name ending in .md results in:

An error occurred while bootstrapping Foam. Error: EISDIR: illegal operation on a directory, read

Steps to reproduce

1. Name a folder with a name ending in .md
2. Clo

Is your feature request related to a problem? Please describe.
Under VIM, I’m used to type :bd to close the current file/buffer.
That command isn’t working under VSCodeVim : Not and editor command bd
To close the current buffer, only :q works which isn’t correct : :q under VIM close VIM (and all files/buffers opened)
:bd seems a better command to close the current file/buffer.

🚀 Feature Proposal

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

• I have searched through existing issues

Feature Request

The new vscode-css-languageservice have many new features.
Need to do:

• provide FileSystemProvider
• provide DocumentContext
• use default css-data, LanguageServiceOptions.useDefaultDataProvider
• use findDocumentLinks2
• use doComplete2
• [

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

Hi, I am developer of VS Code and I am currently going through those extensions which has custom welcome experience (notifications / views) on install. VS Code provides Settings Sync feature OOB and users can have their machines in sync using this feature. So, when user sync such extensions with custom welcome experience, they should not be seeing welcome experience again in their other machines.

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