Is it possible to search the Timeline for two different people or two different events and have them displayed at the same time in order to see their relation to one another?
Yes - and great question[Y]
You can separate them by a comma ( or the word OR) as below
Brilliant! I had tried a comma already, but with a space. And I tried the Boolean AND to no avail. I was close, but apparently not close enough! Thanks!
"AND" is also supported, but will only get you events that match both terms. So « Paul AND Rome » would yield:
Happy hunting!
Hi Eli
Being a standard sort of guy I get caught by the 'space in searches' feature quite often.
Please put in the ideas box in the back of your mind that the software deal with spurious spaces for those of us withahabitofseparatingourwords.
[Y]
I haven't encountered this issue yet, but yes it shouldn't matter whether there's a space after the comma or not. (This reminds me of how annoying it is when a form on the web complains at me for putting dashes or spaces in my credit card number. C'mon, folks. How hard is it to strip them out in the software? Probably no harder than checking if they were there in the first place so that you could put up an error message about it.)
I haven't encountered this issue yet, but yes it shouldn't matter whether there's a space after the comma or not.
cf
as a trivial case!
I haven't encountered this issue yet, but yes it shouldn't matter whether there's a space after the comma or not. cf as a trivial case!
Yes, I know about that one. I was talking about the space after comma, which I'd never known was an issue.
BTW, the no spaces after a colon rule makes some sense to me (as a developer). I think of the filter (author:, title:, etc.) as being tightly bound to the thing it precedes ("tightly bound" meaning/implying higher operator precedence than the AND), so a space would make it ambiguous whether the filter word is something you're searching for or the modifier of the word it precedes. However I can also understand as a user that normal people don't think that way. And I can also understand as a developer that the colon after the filter should unambiguously identify it as a filter.
But a comma implies looser binding (in my mind) than a colon, so a space after it shouldn't make any difference. In fact, I'm able to use the list operator with spaces after the commas in a normal search with no problem:
And, actually, it appears that YesYouNeedJesus was wrong in thinking that doing it with a space after the comma made a difference even in Timelines. I can put as many spaces as I want after it, and it doesn't change the results. YYNJ must have been doing something else wrong, then.
And, actually, it appears that YesYouNeedJesus was wrong in thinking that doing it with a space after the comma made a difference even in Timelines.
Rosie, good catch. I'm not sure what happened, because I tried everything to get this to work. The first thing I tried was the comma with a space. Weird.
We'll see what we can do, thanks!
