Closed mpereira closed 3 years ago
Interesting... This actually gives me a score of 100
, which is very weird. I think is an issue from parsing layer but I am not confident with it. Let me investigate a few days and I will get back to you ASAP!
Thanks for looking into it!
I can also confirm this behavior. The behavior is broken for larger files. And it does indeed return a score of 100.
Sorry for the late reply!
I am currently busy with something else and not having sufficient of time to contribute to this project. I will try to resolve this issue as soon as I have time to do it! Sorry for the inconvenience! 😖
No worries, and no pressure! We all have lives to live. 🙂
I investigated this issue and found that, if an Org document contains at least one colon character (":"), flycheck-grammarly
stops working. If I replace all colons with nothing (""), flycheck-grammarly
works again, even with the most complex documents.
P.S.flymake-grammarly
has this bug too.
I investigated this issue and found that, if an Org document contains at least one colon character (":"), flycheck-grammarly stops working. If I replace all colons with nothing (""), flycheck-grammarly works again, even with the most complex documents.
@salutis If this is true, I can apply quick patch by replacing all :
to something else (maybe a comma ,
). Do you think this will work? Thanks for your hard work by further investigate this issue! 😖 👍
@mpereira @PreciousPudding Can someone confirm this action?
@salutis If this is true, I can apply quick patch by replacing all
:
to something else (maybe a comma,
). Do you think this will work?
I think so. My workflow now is to replace all colons locally to a temporary string, then fix my grammar, and then replace the temporary strings back to colons. It would be fabulous if flycheck-grammarly
could do that for me.
As for using a comma, I am not sure. For instance, the sentence
The colors of buses are: red, green, and blue.
is correct, but the sentence
The colors of buses are, red, green, and blue.
raises a warning in Grammarly.
I would suggest to replace all colons with some other Unicode colon. (Or better, investigate what is happening, if the error is on our side.) I tried two colons from this list and Grammarly did not raise a warning:
raises a warning in Grammarly.
Yeah, that's a rash decision. Should probably replace with something else.
The solution should be simple, by wrapping (buffer-sting)
should work 😕
The only thing we need to concern is what character should use to replace colons :
and the character must be the length of 1
, so we can keep the result the same without needing to re-calculate the error point. @salutis Would you mind doing some test for this? 😕
Anyway, feel free to open a PR if you already have the fix! 👍
This issue should be fixed in 5568feaa5e71cf58e4d89a5aa92e2242250bd02c.
This issue should be fixed in 5568fea.
Thank you so much! ❤️
Hi,
Thanks for writing this package, it looks like it could be very useful for my use cases. I was unable to get it working with files that contain anything more than simple sentences. Maybe it's due to something in my environment?
With this configuration:
and this text (from https://orgmode.org/worg/org-tutorials/org4beginners.html, added first paragraph)
enabling
flycheck-mode
doesn't do anything. Changing the text tocorrectly shows the flycheck error: "Your sentence appears to be missing a verb."
I have also tried exporting the document to Markdown and the behavior is the same.
Please let me know if you need more information.
flycheck-grammarly.el