inline search not working
Lately, I cannot get the inline search to return results.
Macbook Pro (mid 2014), OSX 10.10.2, 2.3 i7, 256 SSD, 16GB RAM, Graphics: Intel Iris Pro 1536 MB
Logos Bible Software 6.1 – 6.1.0.0016
Comments
-
Is it just inline search or morph search in general?
0 -
-
I duplicated this search and it works for me. I have 6.1, Windows version. Not sure why it does not work for you. I wonder whether this is mac related.
0 -
Brian W. Davidson said:
Just inline.
Does it work from the Context menu i.e. selecting the word in Lev 26:18 and getting an inline search for <Lemma = lbs/he/יסר:1>?
Dave
===Windows 11 & Android 13
0 -
-
Restarted the computer?
Dave
===Windows 11 & Android 13
0 -
-
I wish I knew more about indexes. Dave might have suggestions as to which you could attempt to rebuild in case the file has been corrupted.
0 -
Brian
Does Inline search work with any other bible?
Does Morph/Bible Search work for all bibles?
Dave
===Windows 11 & Android 13
0 -
Inline is completely out of commission for me — in all Bibles and all variations of inline, morph, bible, basic.
Morph search in a search window works for all of them.
0 -
This appears to be a License issue rather than an Index issue (an L6 package/Crossgrade is needed for Inline Search). Try the update resources command and get in touch with Tech Support if that fails
Dave
===Windows 11 & Android 13
0 -
Tech support manually started a partial index, but that didn't work.
A "rebuild index" did the trick.
Problem solved. Thanks, all!
0 -
Brian W. Davidson said:
A "rebuild index" did the trick.
Needless to say, it makes as much sense to me as it does to you!
Dave
===Windows 11 & Android 13
0 -
The Morph Search panel uses the Bible Index; Inline Search (and hit highlighting in resources) always uses the Library Index. The latter index must have been corrupted.
0 -
I presume then that I have a similar problem?
I am doing a basic inline search for a single word and it gives no hits, when I can clearly see the word in the TOC (chapter 8). I have even navigated to that chapter and copied the word into the inline search box ... and still no results!!!
I am concerned that the index files seem to be so often corrupted. I am happy that it is not a hardware issue. I presume (no manual ... time to duck!) that the command 'rebuild index' will fix it ... but it kind of takes a few hours (time to duck again!)! But then how can I be sure that it will be fine tomorrow when I search again? Of the various issues that have not been resolved since L4, and the various issues that have been added in L6, the reliability of searches is my chief concern ...
BTW. I have just started 'rebuild Index' and L6 has crashed whilst I was writing this. I will attach the logs here since I will not start another thread simply to say 'it crashed again but I was not doing anything at the time!"
4846.LogosLogs.Martin.20150228-074446.zip
[Update: I have just relaunched L6 and it did not seem to acknowledge that a crash occurred. It used to have an error reporting pop-up that asked 'what happened' ... is that still implemented in L6?]
2017 15" MBP, iPad Pro
0 -
Martin Folley said:
BTW. I have just started 'rebuild Index' and L6 has crashed whilst I was writing this. I will attach the logs here since I will not start another thread simply to say 'it crashed again but I was not doing anything at the time!"
There is no evidence of a crash, but the Logos log indicates some conflicting requirements for the Indexer.
Martin Folley said:[Update: I have just relaunched L6 and it did not seem to acknowledge that a crash occurred...
I can't answer your question but let us know what happens.
Dave
===Windows 11 & Android 13
0 -
Indexing has just finished [:D]
'Sufficiency' is now found 95 times in Grudem ... that should be enough for a starter!
2017 15" MBP, iPad Pro
0 -
Martin Folley said:
Indexing has just finished
'Sufficiency' is now found 95 times in Grudem ... that should be enough for a starter!
I hope he wrote more than 1 book because I got zero results[:D]
Dave
===Windows 11 & Android 13
0 -
Inline Search (and hit highlighting in resources) always uses the Library Index. The latter index must have been corrupted.
I figured there was a question I hadn't asked! Yet another mysterious corruption.
Dave
===Windows 11 & Android 13
0
