-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Magic comments to specify blocks of text that LTeX can ignore? #67
Comments
Fixed. Out of curiosity, why couldn't you use |
Thank you for your consideration. Actually, I just didn't know about |
Ah, I see. It's definitely a good feature suggestion, thank you. For most false positives in the preamble, |
Thank you again for all of your efforts and for working on this feature. Will take a look at |
Fix released in 6.0.0. |
Is your feature request related to a problem? Please describe.
Love LTeX, but for large documents with large sections of code-like/computer-generated listings, LTeX goes crazy and flags many spelling/grammar problems. For me, going through the problems list and clicking "Ignore" for every single one is time consuming, or somewhat slow (i.e. after choosing to ignore one specific problem LTeX detected, it took a few seconds to register before the problem is removed from the list... now try to repeat that for 200+ problems).
Describe the solution you'd like
I noticed LTeX supports Magic comments. How about a way to specify via Magic Comments like "LTeX Ignore Start" and "LTeX Ignore end" between blocks of text where we want LTeX to completely ignore spelling/grammar checking. This solution would be sufficient for me. Others might want additional options to ignore certain rules for a particular block of text.
Describe alternatives you've considered
Going through the problem list and clicking ignore one-by-one. It takes way too much time, I often just don't bother with it anymore but it would good to see a clean file.
Additional context
None.
The text was updated successfully, but these errors were encountered: