Bug 4.0b, RC2: "suffer NEAR (Christ OR Jesus)" returns no results
Doing a Bible search for suffer NEAR (Christ OR Jesus) returns no results. On the other hand, suffer NEAR (Jesus, Christ) does return results. I'm sure the former syntax used to work.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
There was a thread yesterday that explained the difference between the two syntaxes. I believe it is working as intended but I certainly may be wrong
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
I understood that thread to say that they were technically different but functionally equivalent. I wonder whether the bug I refer to is the same as this one Bradley refers to.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
I wonder whether the bug I refer to is the same as this one Bradley refers to.
It sounds the same to me.
MacBook Pro (2019), ThinkPad E540
0 -
Mark Barnes said:
I understood that thread to say that they were technically different but functionally equivalent. I wonder whether the bug I refer to is the same as this one Bradley refers to.
Well, I can't believe the results that Morph search gives (in RC2):-
- (@N, @C) BEFORE 3 words lemma:εἰμί gives the same results as (@N, @C) BEFORE lemma:εἰμ;
- (@N OR @C) BEFORE 3 words lemma:εἰμί gives the same results as (@N OR @C) BEFORE lemma:εἰμί.
With that allowance (@N OR @C) gives WRONG results as Bradley stated. But Morph search ignores proximity and my BUG report remains as is!
In Bible Search the OR'd term also gives wrong results. If Bradley has an open case for the Morph OR it should also apply to Bible/Basic search and treat it as comma separated.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
In Bible Search the OR'd term also gives wrong results. If Bradley has an open case for the Morph OR it should also apply to Bible/Basic search and treat it as comma separated.
We do have an open case (several, actually!) to standardise search syntax across all search types.
0 -
Bradley Grainger said:
We do have an open case (several, actually!) to standardise search syntax across all search types.
I'm pleased about that - the sooner the better (4.0c?).
Dave
===Windows 11 & Android 13
0 -
This is getting worse! (Or perhaps it's always been this bad and I haven't noticed before!).
Doing a basic search for ("Graeco-Roman" OR Greek) NEAR spirit treats the NEAR keyword as if it is a normal word 'near'. But ("Graeco-Roman", Greek) NEAR spirit works as advertised.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
This is getting worse! (Or perhaps it's always been this bad and I haven't noticed before!).
It is disguised in a Morph Search of an OL bible eg. (@N OR @C) NEAR lemma:εἰμί, because NEAR does not appear in the surface text, but is only too evident when searching a reverse interlinear. (@N, @C) NEAR lemma:εἰμί also fails!
Uggh!
Dave
===Windows 11 & Android 13
0
