xadillax / vscode-language-viml Goto Github PK

Hi, thanks for developing this extension.

I'd like to change the number of spaces inserted after " to 1 (instead of the default 2). How to achieve this? There seems no option for this?

I tried toggling this setting, seems nothing has changed.

IdeaVim actually uses .ideavimrc as specified in https://github.com/JetBrains/ideavim

So could .ideavimrc be added to supported filetype

And possibly, somedayTM even add it (I'm not aware of any viml extension that has that yet - it would really make the extension stand out).

Currently, \t is inserted after " when using editor.action.commentLine, please use \s instead of \t, that would be a space saver ;).

Repro Steps:

1. Put the cursor at the start of a line.
2. Use "editor.action.triggerSuggest".

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency @types/node to ^20.16.2
• chore(deps): update dependency typescript to ^5.5.4

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hello, would you consider including syntax highlighting for vim-related .vroom test files along with the others?

vroom is a literate testing tool for vim plugins and the syntax is just a thin wrapper around vimscript syntax, that's already supported out-of-the-box in vim.

You should also add the _vimrc file to the supported languages, since it is an alternative to .vimrc.

... and possibly improves on one of the TODO points, providing (at least a bit of) better code-completion.

Doesn't need to contain much but as this shows in the market places it is commonly useful to have it with some minimal content in - and also is a service to the users to know about the updates without checking the git diff. Maybe good to do together with #6.

For details see Publishing Extensions on open-vsx.org, it would be good to have this extension not only in the ms marketplace but also available in a place that does not explicit forbid to use it with anything else than a Visual Studio product or a browser.