Search

I'm using Logos 8 on both Windows and Mac. I've searched all over for a way to control this and I can't find it, but I also can't help but think this must be easy to do. I have a Bible window open reading a passage. In a separate window, I have a commentary or something like the New Treasury of Scripture Knowledge for all its cross references. When

How in the world do I shut this off? I don't recall this ever happening until just recently. I'm on the annual plan so the program updates automatically and one day it just started doing this. If my mouse pointer passes over the word "and," every other instance of the word "and" on my screen highlights. I. Hate. That. So. Much. It doesn't matter if

I presently own Logos 6 Reformed Bronze (plus I've unlocked some other specific books here and there). As I understand it, these are my upgrade options: 1. Buy Logos 7 feature set, for $211 and change. 2. Buy a Logos Now subscription, $99 a year. I understand how that all works. And if I choose either, I can continue to use the library I have right

I'm running Mac OS X 10.10.3 on a current generation MacBook Pro with Retina display. Today, Logos 6 download 5+ GB of updates and something odd occurred. When I put the Logos 6 app icon on the dock and launch it for the first time, it quickly replaces it with an alias icon (the one with the little arrow in the bottom left hand corner). Now it isn't

LHB is the only Hebrew Bible we have that currently has root data. (BHt will have its own root analysis). I haven't really tested the drop down word selector in the Bible Search UI. In the Morph Search tab, it's supposed to only show options that actually occur in the Bible(s) you select for searching, but there's some extra material showing up in that

[quote user="Brian W. Davidson"] Vincent, I know this is minute, but technically there shouldn't be a space between the double brackets and the single brackets in 2+1:5, correct? [/quote] There's no extra space there, actually. It's that the glyphs for those square brackets in this font have really wide margins.

This layout was done by design. Of course, it must be going on a decade ago, so it's an older design. Tables worked a little differently in our software when this was made. But the reason Genesis was done this way was that the verse-by-verse sections of the print had a split between less-technical commentary on the top of the page and more technical

Yes, there is one or more bugs going on here. At least one, I am told, has been addressed in internal builds (to do with unnecessary conversions between lemma data type references that causes some significant loss of hits). But there may be another issue with K/Q pairs not being handled well (note how this result is showing the K surface form, but the

The Andersen-Forbes database is a fantastic resource, and you can still run all the same searches, visual filters, etc. directly on the Andersen-Forbes Analyzed Text. There were a number of reasons why we decided to make our own in-house Hebrew Bible (LHB). One of the most important benefits was to be in control of how the text is broken into segments

This is a syntax search, of course. When you're setting up each 'word' element, make sure to click 'matching skips levels' so you don't have to worry matching all the internal structure. The special sauce is to add an agreement operator to the second word telling it to match the lemma of the first word. You could, of course, use 'sentence' or 'phrase