2 ms·
> "foo bar" is actually treated like "foo" "bar" No it isn't. Compare "internal engine" with "internal" "engine": https://www.google.com/search?q=%22internal+
by gniv 8y ago
> "foo bar" is actually treated like "foo" "bar"
No it isn't. Compare "internal engine" with "internal" "engine":
https://www.google.com/search?q=%22internal+engine%22 https://www.google.com/search?q=%22internal+engine%22
https://www.google.com/search?q=%22internal%22+%22engine%22 https://www.google.com/search?q=%22internal%22+%22engine%22
- ergothus 8y agoYou're correct, it does not work as I describe. My description of the problem was just wrong, so thanks for pointing that out. However, it doesn't work the way it used to either. I get frustrated once or twice a year about this, and every time I fight with the many (old) tutorial examples, but eventually end here: https://productforums.google.com/forum/#!topic/websearch/6gHVUEl8y1k/discussion https://productforums.google.com/forum/#!topic/websearch/6gH... Where we see that "foo bar" only says that "foo" will appear in the text before "bar" (but anything can be between them), and that's assuming the bug is actually fixed. That status of "we think it's fixed and users don't agree" is the last I've ever seen.