Missing search terms?
I'm used to doing search like <bible in "genesis 2:3"> , but neither the "in" nor the "near" search terms work in L4.
"The whole modern world has divided itself into Conservatives and Progressives. The business of Progressives is to go on making mistakes. The business of Conservatives is to prevent mistakes from being corrected."- G.K. Chesterton
Comments
-
NEAR works. IN doesn't.
"The whole modern world has divided itself into Conservatives and Progressives. The business of Progressives is to go on making mistakes. The business of Conservatives is to prevent mistakes from being corrected."- G.K. Chesterton
0 -
Ben said:
I'm used to doing search like <bible in "genesis 2:3"> , but neither the "in" nor the "near" search terms work in L4.
Bradley Grainger of Logos has told us that search syntax is not yet documented for Logos 4. So trying is the best we can do. Some search syntax is exactly as in 3.0 but the <> brackets are not used. Holy WITHIN 5 WORDS Spirit is one that works.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Ben said:
I'm used to doing search like <bible in "genesis 2:3"> , but neither the "in" nor the "near" search terms work in L4.
Specifying the data type is often unnecessary, because Logos 4 can usually figure it out: there's really only one thing (ignoring versification differences, which are handled automatically, anyway) that you can mean by "Genesis 2:3". For a data type reference search, enclose the reference in angle brackets:
<gen 2:3> <G3056>
etc. To force an exact (not an intersecting) match, use an equals sign:
<= Jn 3:16>
If you need to distinguish ambiguous references, you can still specify the data type name/alias, optionally followed by an operator, then the data:
<LN = 1.10> <tdnt = 1.10> <LN ~ 33.98> <LN 33.98>
0 -
Bradley Grainger said:
For a data type reference search, enclose the reference in angle brackets:
<gen 2:3> <G3056>
etc. To force an exact (not an intersecting) match, use an equals sign:
<= Jn 3:16>
If you need to distinguish ambiguous references, you can still specify the data type name/alias, optionally followed by an operator, then the data:
<LN = 1.10> <tdnt = 1.10> <LN ~ 33.98> <LN 33.98>
Wow--thanks, Bradley! Where would I find tips like this--help? help videos?
Blessings, & THANKS for all you do for us!
Bill
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
Bill Stonebraker said:
Wow--thanks, Bradley! Where would I find tips like this--help? help videos?
It will be in the help... eventually. (I think one of the items on my tasklist is to review and flesh out the existing help on searching but I haven't gotten to it yet...)
0 -
Bradley,
I did a quick HELP and would appreciate your comments at http://community.logos.com/forums/t/4193.aspx
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
I did a quick HELP
Wow--THANKS, Dave! I've bookmarked that page...
Thanks again!
Bill
Grace & Peace,
Bill
MSI GF63 8RD, I-7 8850H, 32GB RAM, 1TB SSD, 2TB HDD, NVIDIA GTX 1050Max
iPhone 12 Pro Max 512Gb
iPad 9th Gen iOS 15.6, 256GB0 -
It seems that <luke 13:1-9> gives the same results as <bible in "luke 13:1-9"> used to in L3
0 -
CoramDeo said:
It seems that <luke 13:1-9> gives the same results as <bible in "luke 13:1-9"> used to in L3
Yes, both are an "intersection" search.
<luke 13:1-9> is the "friendly" syntax for <bible ~luke 13:1-9> - see http://wiki.logos.com/Search_HELP
Dave
===Windows 11 & Android 13
0
