Support match for end keywords

[faustinoaq]

Hi community!

I'm happy user of Vim and VSCode 😄

On Vim I can match Ruby, Crystal, Elixir, Lua, Julia end keywords using matchit.

By example, the following code is in Crystal on Vim:

Would be nice to have something similar on VSCode.

My proposal is something like autoClosingPairs configuration allowing open and close info:

{
  "comments": {
    "lineComment": "#",
    "blockComment": ["=begin", "=end"]
  },
  "brackets": [
    ["{", "}"],
    ["[", "]"],
    ["(", ")"],
    { "open": ["do", "if", "else"], "close": "end", "notIn": ["string", "comment"] }
  ],
  "autoClosingPairs": [
    ["{", "}"],
    ["[", "]"],
    ["(", ")"],
    ["`", "`"],
    { "open": "'", "close": "'", "notIn": ["string", "comment"] },
    { "open": "\"", "close": "\"", "notIn": ["string"] }
  ],
  "surroundingPairs": [
    ["{", "}"],
    ["[", "]"],
    ["(", ")"],
    ["\"", "\""],
    ["'", "'"],
    ["`", "`"]
  ]
}

Thanks for this great editor! 👍

[faustinoaq]

@kieferrm So you think would be possible to achieve this with an extension?

[kieferrm]

@faustinoaq I'm guessing you refer that from the editor-contrib label. This label is referring to the internal structure of our editor (core with contributions on top). Extensions can not provide this kind of editor contributions. Putting this aside, an extension could implement this functionality although not exactly the way you describe it as the API surface of language configuration is limited.

[rebornix]

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!