repeated word rule doesn't fire

[notuntoward]

Repeated words aren't detected, although I have this rule turned on. Below, "accurate" is repeated.

[grantlemons]

Currently, our implementation only considers certain commonly repeated words for this lint. I can try to reimplement this such that it will check all words, but a more immediate step that should be taken is updating the description for the setting to make it clear that it only considers commonly repeated words.

Currently checked words:

"the", "be", "to", "of", "and", "a", "in", "that", "have", "I", "it", "for", "not",
"on", "with", "he", "as", "you", "do", "at", "this", "is", "but", "his", "by", "from",
"they", "we", "say", "her", "she", "or", "an", "will", "my", "one", "all", "would",
"there", "their", "what", "so", "up", "out", "if", "about", "who", "get", "which",
"go", "me", "when", "make", "can", "like", "time", "no", "just", "him", "know", "take",
"people", "into", "year", "your", "good", "some", "could", "them", "see", "other",
"than", "then", "now", "look", "only", "come", "its", "over", "think", "also", "back",
"after", "use", "two", "how", "our", "work", "first", "well", "way", "even", "new",
"want", "because", "any", "these", "give", "day", "most", "us", "are",

[elijah-potter]

Hey @notuntoward,

Sorry for the delay in getting back to you on this. Things have been a little hectic.

We've just released Harper v0.13.0, which incorporates some significant improvements to this rule, thanks to @grantlemons.
Would you mind testing to make sure you don't get any more false-negatives like this so we can close issue?

[notuntoward]

@elijah-potter , Thanks. Unfortunately, it still doesn't work for me in this example:

this paper shows that, while the method may be more accurate accurate, the turnout overestimate suggests that self-selection bias is not sufficiently reduced.

"accurate" is typed twice but the repetition isn't detected.

But I should note that I had difficulties updating -- the install procedure stalled on Harper. When I restarted obsidian, then I got a message saying something like "Harper cannot be restarted," After uninstall and then reinstall, Harper did restart, and appeared to be the newest version (1.3.0). But maybe it's not, really?

[grantlemons]

Ah, the obsidian plugin seemed to have had a large problem on 0.13.0 (#338), but @elijah-potter has pushed out 0.14.0 which should hopefully resolve the issue.

In my local tests I found that harper linted your example correctly, so if you update the obsidian plugin to the 0.14.0 version, it will probably work as intended.

[elijah-potter]

@notuntoward, would you mind confirming that the issue has been fixed on your end so we can close it out? Thanks again for letting us know about it!

[notuntoward]

With 0.15.0, it still doesn't detect the repeat. This is on Obsidian.