You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2024. It is now read-only.
Whenever I type something like 123~things in TeX (i.e., using the non-breaking space ~ to bind the number to the word), the Grammarly extension reports that as an error and wants to "correct" it to 123 things.
I'm not sure if the extension could catch this issue by "pretending" to the Grammarly API that the non-breaking space were a normal space, but if that's possible, it would help me enormously!
However this goes, I really appreciate your work on brining Grammarly to VS Code. It really boosts my technical writing workflow! 👏 🥳
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Whenever I type something like
123~things
in TeX (i.e., using the non-breaking space~
to bind the number to the word), the Grammarly extension reports that as an error and wants to "correct" it to123 things
.I'm not sure if the extension could catch this issue by "pretending" to the Grammarly API that the non-breaking space were a normal space, but if that's possible, it would help me enormously!
However this goes, I really appreciate your work on brining Grammarly to VS Code. It really boosts my technical writing workflow! 👏 🥳
The text was updated successfully, but these errors were encountered: