Bug in search?

wsbones

Beta Tester
#1
When I have the option in Bible Panel/Additional options set to Remove hyphenation

upload_2018-5-19_12-2-45.png


An exact search for a phrase like "inhabitants of Jabeshgilead" does not work.

upload_2018-5-19_12-6-16.png


It also doesn't work if I specify exact phrase rather than using quotes.
 

marty

Beta Tester
#3
I tried the search after changing my settings to remove the optional hyphen and it would find "Jabeshgilead" but the word wasn't highlighted in the verse list. It wouldn't find "inhabitants of Jabeshgilead" but did find Jabeshgilead with a search for "Jabesh*" (still no highlights).
 

Brandon Staggs

Administrator
Staff member
#4
I have confirmed that this is a bug with the "Remove optional hyphenation of compound names" setting. Thank you for the report.
 

wsbones

Beta Tester
#5
I think I found another small bug. It seems like you can't reuse a module shortcut after you delete it.

I renamed a user module from FAVORITE to FAV. I had a module shortcut set up to open the module, FAVORITE (alt-q). After renaming, the shortcut no longer worked so I deleted it and set it up again using the same shortcut (alt-q). Everything looked right but the shortcut did not work. I repeated the whole process, but it didn't work. It said the user module FAVORITE was not found even though the shortcut dialog said that alt-q was a good key combination.

I created a new module shortcut alt-z and that worked to open FAV.

Then I deleted alt-z and tried to reuse alt-q. It still did not work.

Then I tried to assign alt-z to to TSK. That did not work.
 

wsbones

Beta Tester
#6
Will the hyphenation bug fix also fix word trees? Try a word tree for Bethlehem in the book of Ruth.

Could the fix work regardless of the setting in Bible Panel/Additional options? If a user module has search links/tree links, it will fail in some cases depending on the setting.
 

Brandon Staggs

Administrator
Staff member
#7
The word tree needs some special processing to match on hyphenation optionally. But once I address this issue in the module search code it should work fine across the board regardless of the search source. I am think that realistically, there shouldn't be a need to distinguish hyphens in a word tree, so they should probably just be ignored regardless of this setting.
 
Top