grammarly: Grammarly is not changing the dialect
I’ve configured Grammrly to British dialect
However, I didn’t take effect even after reloading Vscode
The output log:
Ready!
Initializing...
Initialized!
open file:///home/tapyu/tst/test.txt
create text checking session for "file:///home/tapyu/tst/test.txt" with {
"documentDialect": "british",
"documentDomain": "general",
"suggestionCategories": {
"conjugationAtStartOfSentence": "off",
"fluency": "on",
"informalPronounsAcademic": "off",
"missingSpaces": "on",
"nounStrings": "on",
"numbersBeginningSentences": "on",
"numbersZeroThroughTen": "on",
"oxfordComma": "off",
"passiveVoice": "off",
"personFirstLanguage": "on",
"possiblyBiasedLanguageAgeRelated": "on",
"possiblyBiasedLanguageDisabilityRelated": "on",
"possiblyBiasedLanguageFamilyRelated": "on",
"possiblyBiasedLanguageGenderRelated": "on",
"possiblyBiasedLanguageHumanRights": "on",
"possiblyBiasedLanguageHumanRightsRelated": "on",
"possiblyBiasedLanguageLGBTQIARelated": "on",
"possiblyBiasedLanguageRaceEthnicityRelated": "on",
"possiblyPoliticallyIncorrectLanguage": "on",
"prepositionAtTheEndOfSentence": "off",
"punctuationWithQuotation": "on",
"readabilityFillerWords": "on",
"readabilityTransforms": "on",
"sentenceVariety": "on",
"spacesSurroundingSlash": "on",
"splitInfinitive": "on",
"stylisticFragments": "off",
"unnecessaryEllipses": "off",
"variety": "on",
"vocabulary": "on"
}
}
text checking session for "file:///home/tapyu/tst/test.txt" is ready
ready file:///home/tapyu/tst/test.txt
connecting file:///home/tapyu/tst/test.txt
checking file:///home/tapyu/tst/test.txt
idle file:///home/tapyu/tst/test.txt
connecting file:///home/tapyu/tst/test.txt
checking file:///home/tapyu/tst/test.txt
About this issue
- Original URL
- State: open
- Created 8 months ago
- Reactions: 14
- Comments: 17
I just downgraded from 0.24.0 to 0.22.1 and this issue disappeared. There is a bug in the 0.24.0 version
Hope this gets fixed soon.
That, I don’t know. The Grammarly account is probably owned by @znck. So he may have insights about it.
EDIT: It’s honestly surprising that it still works…
I am encountering this issue, too, and I would love to see it fixed. Thank you!
Still happens here too
Same here. I Downgraded to v.0.23.10, and it’s all good now. Hope this will fixed in the next release