The + operator has been replaced.

Re:The + operator has been replaced. by moultano on Saturday October 22, 2011 @10:07AM (#3143528)

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.

[ Parent | on HN ]

Re:The + operator has been replaced. by unfasten on Monday October 24, 2011 @09:03AM (#3149414)

I'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.
    """

[ Parent | on HN ]

Re:The + operator has been replaced. by maggit on Monday October 24, 2011 @04:13PM (#3151370)

Ok. 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.

[ Parent | on HN ]