Do you know what's going on?
xyz finds results that are listed in the text only and not the code part, unless that code part is set using the
</pre> tags. So, this type of search excludes code segments that are not set via the
</pre> tags (indented by 4 spaces).
If you want to search within those segments, you need to use
code:"<code>". This, however, requires an exact match for a code segment. So searching for
code:"xyz" would miss code segments with
xxyz in it.
In-line code content (those between backticks
`<code>`) seem to fall within both categories.
The difference here stems (I guess) from the fact that there's two different versions of question content that is active in the background - a "raw" and a "baked" format. The latter is an HTML (or visual/display) format for representing content within the browser, while the latter is the content as-is.
You can't combine these searches, since the OR operator is only used for combining tags (as in,
[widgets] or [geegaws]).
Here are some choices:
It is often better to search using a site-specific Google search, as in
"cs_set_eq" site:tex.stackexchange.com. However, since questions and answers are contained within the same visible page, the search results will necessarily cover both (as opposed to having a
Searching is definitely not perfect on the network and takes some practice getting used to. Escaping characters may also cause issues, and this is especially true on TeX.SE where the use of
\ is prevalent.