Skip to content
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

Fix block boundary bug introduced by Unicode refactoring #334

Merged
merged 1 commit into from Jul 30, 2020

Conversation

hannahbast
Copy link
Member

@hannahbast hannahbast commented May 3, 2020

After 45a68f6, the block boundary computation was no longer correct: there was always one block per word. I stumbled upon this when a freshly build index with text no longer supported the * in the argument of ql:contains-word

It seems to me that there was simply one line missing, please double-check

TODO: add a unit text that checks that the block boundaries are not the trivial boundaries (one block per word)

After 45a68f6, the block boundary
computation was no longer correct: there was always one block per word.
I stumbled upon this when a freshly build index with text no longer
supported the * in the argument of ql:contains-word

It seems to me that there was simply one line missing, please double-check

TODO: add a unit text that checks that the block boundaries are not the
trivial boundaries (one block per word)
Copy link
Member

@joka921 joka921 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great find, classic bug in a classic pattern

@joka921 joka921 merged commit 7797474 into master Jul 30, 2020
@hannahbast hannahbast deleted the f.fixTextBlockBoundaries branch September 29, 2021 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants