-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not Working with Madoko Document Type #85
Comments
Unknown document types cannot be enabled without adjusting the code. This is VSCode's limitation. I will do this as soon as possible. |
Thanks for your reply. I'm not sure if I'm understanding you correctly but the extension actually adds a new document type, no?! See this excerpt (from here): "contributes": {
"languages": [
{
"id": "madoko",
"aliases": [
"Madoko",
"madoko"
],
"extensions": [
".mdk",
".madoko"
],
"configuration": "./language-configuration.json"
}
],
"grammars": [
{
"language": "madoko",
"scopeName": "source.madoko",
"path": "./syntaxes/madoko.tmLanguage"
}
]
} |
If I understand things correctly the extension for Madoko you pointed out adds new document class The problem with VSCode is that so far it does not give access to all the registered (by the editor itself and by the extensions) document classes. It would be great if VSCode would give access e.g. to semantical inforamtion like how are line/block comments constructed etc. |
Okay, I think I know what you mean. :) |
Added in just released version 2.0.0. Please give some feedback if it works for you. |
Thanks, it's working now. Though some Madoko specific syntax is checked too. Would it be possible to use the Madoko syntax support instead of Markdown (if installed)? |
As I have noted above first part of the problem is that VSCode does not allow extensions to use the information about document class (e.g. line/block comments, strings, quoting etc.) So there is no way to parametrize my parsers to an unknown language. Can you show me a sample (both screenshot & source of the document) demonstrating the problem? |
Sorry for the late reply. Of course, here is an example (source Test.mdk.txt): It would be great if all the errors would go away. Ideally only headlines and text blocks (excluding special inline blocks such as references) would be checked. |
I'm using the Madoko for VSCode extension and having trouble getting the spell checker to work.
It's actually working fine with Markdown and other formats. Just Madoko seems to make trouble. I already tried enabling it by default for the document type using
"spellright.documentTypes": ["madoko", "markdown", "latex", "plaintext"]
and the status bar info suggests it's activated. However absolutely no error is shown for obviously wrong words.Any ideas on what might be wrong?
The text was updated successfully, but these errors were encountered: