-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Error in Output #16
Comments
Most likely this is artifact after #14. //cc @tengattack if you're interested |
Could you try to remove the last two plugins:
And try again? See whether the errors have gone |
BTW, you should remove the MY config works fine:
|
That sounds like something that should be in the documentation though |
Yes. It only works in limited scenarios now. I will update the README later. |
Okay and for frontmatter?
Still gives me the "Headings should use atx" warning even though it should not anymore |
Could you remove the first "frontmatter" plugin, only keep |
That gives the same message here |
What about using remark-cli, run the |
Nope, remark-cli gets it right! |
Wait, I ran into a different issue again. I need to reload the window every time I update the config file for it to be used by the vs code extension. Something I previously reported here drewbourne/vscode-remark-lint#2 After reloading the window and just using |
Currently, Yes, you will need to reload window every time after config updated. |
I will dig into it later, it seems the settings didn't pass to the plugin. |
That maybe should also be in the readme since it's really not intuitive. What's the reasoning for it? And if it's required maybe add a notification or button to reload when the config changes? |
Could you try to add the settings |
Added "remark.format": {
"plugins": [
"frontmatter"
],
"type": "custom",
"marker": "-"
} to my VSCode config, reloaded and now it works :) |
@tengattack any news here? 😃 |
@Stanzilla, if you run the following commands in the root folder of your project, what's the output in your console? npm install remark-cli
npx remark-cli . |
That works but it's been a while since I had this problem, I haven't used remark since then. |
Please try version 1.3.0 of unifiedjs.vscode-remark (notice the rename). If that does not fix this problem, please reopen the issue. |
Getting these errors in the output in VSCode:
My config file looks like this:
The text was updated successfully, but these errors were encountered: