Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ignore Code Blocks in Markdown #26

Closed
ishehadeh opened this issue Feb 23, 2020 · 2 comments
Closed

Ignore Code Blocks in Markdown #26

ishehadeh opened this issue Feb 23, 2020 · 2 comments
Assignees
@valentjn
Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch

Comments

@ishehadeh
Copy link

Is your feature request related to a problem? Please describe.
Code blocks usually can't be grammar checked accurately, but they are not ignored by vscode-ltex.

Describe the solution you'd like
I'd like the option to ignore everything between back ticks, when checking markdown.

Describe alternatives you've considered
None

Additional context
None
@ishehadeh ishehadeh added the 1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature label Feb 23, 2020
@valentjn valentjn self-assigned this Feb 29, 2020
@valentjn valentjn added the 3-fixed Issue resolution: Issue has been fixed on the develop branch label Feb 29, 2020
@valentjn
Copy link
Owner

valentjn commented Feb 29, 2020 •
edited
Loading

@IanS5 Thanks for the suggestion! The upcoming release of LTEX will bring quite a few changes (that means hopefully improvements...) to the handling of Markdown documents. The change relevant to this issue is that there will be ltex.markdown.ignore and ltex.markdown.dummy settings that will work analogously to the existing LATEX ignore/dummy mechanism. By default, code blocks (```...```) will be ignored, while auto-links (<https://...>) and inline code (`...`) will be replaced with dummy words. This can be overridden by the new settings.

@valentjn
Copy link
Owner

Fixed in 4.7.9.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@valentjn valentjn

Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ishehadeh @valentjn