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.
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
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.
I wonder whether the bug I refer to is the same as this one Bradley refers to.
It sounds the same to me.
Well, I can't believe the results that Morph search gives (in RC2):-
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.
We do have an open case (several, actually!) to standardise search syntax across all search types.
