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

Seeing marks, ideally in the gutter, but maybe as a highlight or something, would be helpful. This apparently existed at one point (https://github.com/vscodevim/Vim//commit/713f30a1a8f4923dfc2e7b0cbceffce78ab83c01#diff-a7723f32fe6b05e135838f84e5c23c0fR870), but decoration options have gotten richer and we can put it under a setting.

🚀 Feature Proposal

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

• [X ] I have searched through existing issues

Feature Request

At the moment it seems that the vti diagnostics command only accepts directories as an argument?
E.g., running vti diagnostics src/components/ will check all .vue inside the src/components directory. Passing a single file as an argument results in an ENOTDIR exception. It would be helpful to pass single files or a list of sin

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

This is related to the issue #1606 - Update icon of AL language
We got even newer version of it so it would be nice to have it in VS Code.

Here you can find png and ico files

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

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

Similar to microsoft/vscode-pull-request-github#1622, have the same behavior for the queries in the PR tree