-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Textidote #3376
Textidote #3376
Conversation
Maybe add to TODO list to make the pull work with markdown as well? That's the reason I suggested to remove standalone languagetool from markdown files, to pick textidote instead. |
@oblitum Oh 🤦 of course. I honestly didn't even know it's possible. I have committed once or twice to the project, but I am just using it with latex so far. This will be great for my markdown notes :). I will add it to the TODO list and see if I find time. I'm very busy the next weeks, so I can't make any promises about the tests and the markdown feature. So PRs to my textidote branch are definitely welcome! Edit: Feel also free to submit a PR (or commit directly, if you have access rights, I'm not sure) if you want to remove the |
@bratekarate I have no commit access, and not much time either :/ |
This pull request has been automatically marked as stale because it has not been updated recently. Make sure to write tests and document your changes. See |
TODO
Edit: Need help with the linter with regards to the doc files. I don't really understand what needs to be changed.Nvm, fixed it. Does anyone know why the linter always fails locally for me with the following doc diff:
Only an issue locally, not a problem but a little annoying to always have a false negative.