Hot answers tagged

13

The reason you don't get good results using the Stack Exchange internal search facility is because a single general-purpose search engine is common to all SE sites. Some of the things it does (ignoring short words and punctuation marks, etc.) are a net benefit on most other sites, but not on ELU. So I don't usually bother with them. Google's "site-specific" ...


8

The Help Center really only covers the most basic stuff (the list of privileges is pretty good though). You can get better results by searching Meta. It's worth noting that you'll get more (and often better) results on the Main Meta or Meta Stack Overflow. They're working on improving search as part of the Channels project on Stack Overflow: I can vouch ...


6

The best way to search is to use Google, rather than the site search in the top-right corner. When using Google, you need to specify the site you want the results to come from, using the site: parameter. The following is a suitable search, although it should all be on one line and entered as a single string into the search box: past tense has a boundary ...


4

This will be fixed in the next deploy.


3

Use the search term closed:yes (or as Dan Bron suggests, closed:1). The Search page itself contains some tips when you click the 'Advanced Search Tips' link on the right: You can use it e.g. to exclude questions which are closed as duplicates.


3

Yours is an interesting point, but I’m not wholly sure we want this fixed. The technical explanation for what I believe is happening is probably going to either confuse or bore the pants out of most people reading this, but here goes anyway. I’m pretty sure that Stack Exchange searches are done using something called the Unicode Collation Algorithm at ...


3

If I understand this correctly The SE search engine ignores a finite number of words—stop words—such as articles, particles, perhaps prepositions and copulae and so forth But in many cases these stop words themselves are the subject of our posts, and are precisely the key words an ELU user might employ in a search A cheap and easy workaround is ...


2

If keywords will be listed at the bottom of a post, then as StoneyB said, who cares how they're formatted? The current behavior is fine. If keywords will be embedded in running text -- that is, you're asking people to use <code> to flag keywords in the body of the post -- then you should not change the formatting at all. Keywords are meta-...


1

Useful tips preserved from comments to the question: I put "well received question" in the Meta search bar and got relevant results. You have to be smart about which site you're searching for what sort of topic. Discussion on meta is far more likely than the help center to answer questions about community standards. Once you get the hang of the search ...


1

I am pasting Dan Bron's very helpful comment as an answer here because a comment can disappear anytime: Go to the search bar. Type closed:1. Pick your sort (eg by votes, by newest). Voila


1

Why not treat anything already between quotes as 'searchable'? That is, in the tokenizer throw out stop words as usual except tokenize everything that is already quoted: single, double, italic, bold, code, whatever. That way, there is no laborious editing that needs to be done by anybody by hand, no need to educate people (which will be long hard and won't ...


1

I'm one of those who never uses code markup on ELU because (1) frankly, it looks ugly, and (2) it's pretty well-ingrained on the web that "a bit of typewriter font in the middle of proportional-spaced text" is synonymous with computer code, and is thus not really appropriate on ELU. Apparently, this means that I've been unknowingly disabling the search ...


Only top voted, non community-wiki answers of a minimum length are eligible