3 ms·
We've looked at data like this. I'm trying to get examples from the community to supplement it. Looking at aggregate statistics isn't a great way to measure wha
by moultano 15y ago
We've looked at data like this. I'm trying to get examples from the community to supplement it. Looking at aggregate statistics isn't a great way to measure what's bothering power users.
- unfasten 15y agoI've saved a few searches where autocorrect gets too aggressive. I've run in to more than this but I don't save all since usually I just want results for my search immediately and don't feel like recording them: I needed `+pyinotify` on this one to get the results I requested. I've come across this problem with quite a few other python packages but I can't recall them at the moment.: Search: pyinotify thread Result: Aggressive correction; wrong `Showing results for inotify thread. Search instead for pyinotify thread` This one isn't exactly related but automatically changing negated terms is frustrating: Search: win 7 processor not +downclocking -gpu Result: bad autocorrect """ Showing results for win 7 processor not +downclocking -cpu. Search instead for win 7 processor not +downclocking -gpu. """
- moultano 15y agoThanks!
- maggit 15y agoOk. Got it. An example for you: "libtelldus no symbols" gives me three absolutely unrelated results for my top hits, confusing me enough not to register the following five related hits.