Thanks, I know it's not so popular yet, but if it's okay, I will keep this PR opened until it meets your requirements.

searching for path:*.vento now shows 2.3k results

I think what @boehs is getting at is that number of files (2.4k is what I'm seeing) under https://github.com/search?q=path:*.vto&type=code would put Vento popular enough under what I understand to be the current requirements (#5756).

https://github.com/search?q=path:*.vto&type=code shows 2.7K now.

https://github.com/search?q=path:*.vto&type=code shows 2.7K now.

Usage isn't an issue now. Lack of action on the initial review overall year ago is what is holding this PR back.

This PR has been marked as stale and will be closed if issues aren't addressed by the time of the next release.

@lildude I've made some changes and I think all your comments have been addressed.
Can you confirm if everything is okay?
Thank you!

@lildude done!

@lildude I just resolved some merge conflicts. Let me know if more changes are needed.
thanks!

Re-adding the grammar using script/add-grammar by replacing it with itself should resolve these test failures.

@lildude thanks! I think it's fixed now (the tests pass in my codespace)

@lildude thanks! I think it's fixed now (the tests pass in my codespace)

🤔 the vendor/README.md file update is missing (the tests should fail in a mo). Looks like you forget to commit and push the changes to this file.

@lildude The add-grammar command removed this entry in the README.md file. I added again and the tests failed, so I assumed it should be removed (here).

Do you want me to add it again?

@lildude The add-grammar command removed this entry in the README.md file. I added again and the tests failed, so I assumed it should be removed (here).

Do you want me to add it again?

Oh, I think I can see the problem… you've not set tm_scope in languages.yml.

I followed the following instructions:

# tm_scope              - The TextMate scope that represents this programming
#                         language. This should match one of the scopes listed in
#                         the grammars.yml file. Use "none" if there is no grammar
#                         for this language.

What value should be there?

It’s the scopeName from the grammar which is automatically found and added to the grammars.yml file but needs to be manually set here as a repo can have more than one grammar scope as is the case here.

Ok, I think it's good now 🤞

Is it expected that the HTML part of the syntax highlighting isn't working? The Vento tags are now being highlighted but the rest isn't:

Is it expected that the HTML part of the syntax highlighting isn't working? The Vento tags are now being highlighted but the rest isn't:

That would need to be a question you would need to raise with the upstream grammar.

The VSCode extension correctly highlight HTML code.
The pattern for html is included here.

@lildude is this supported by GitHub or maybe there's another way to inject HTML as the top level grammar of Vento?

The VSCode extension correctly highlight HTML code. The pattern for html is included here.

@oscarotero the scope used for html in the grammar you linked is text.html.derivative, it's a scope that is available in VS Code via this file, but it is not a scope available in the grammars compiled by linguist.

Thanks @DecimalTurn
After inspecting the other grammars, it looks like the right scope should be text.html.basic, right?

Since the scope text.html.basic is referenced inside the grammar for the text.html.derivative scope, you'd need to make sure that both of these are included in the grammars that Linguist loads to get complete html support.