SearchCode Relevancy Error about zeroclickinfo-spice HOT 12 CLOSED

No there would be none. Titles generally have a much greater weight assigned to them and would appear at the top.

We are getting into trying to understand what the user is typing here..... What if the spice is modified so that if it triggers, if the remainder of the search is less then 3 characters it ignores it?

It would clean up this one and other similar ones I suspect. It would however still let things like,

iOS 6 date

through though, but perhaps a spice to pick up "date" and return news results would be a way to overide this. Is there some way to specify which spice wins when it comes to results?

from zeroclickinfo-spice.

Actually that's something we're just working on right now so we are able to let them race or give other spice's the advantage. I'll have to play around with SearchCode and see what I can do. Thanks!

from zeroclickinfo-spice.

Awesome.

from zeroclickinfo-spice.

Closing as this is no longer handled by a spice (and the result given now appears highly relevant to me). Please reopen if that wasn't the intended plan :-)

from zeroclickinfo-spice.

@nospampleasemam this is still handled by the SearchCode spice, but wiki gets priority on this result. However, SearchCode didn't even trigger...

from zeroclickinfo-spice.

It is triggering... and if you step through the spice code it renders as expected. However if you clear cache etc.. and rerun you get the following error,

Line: 1
Error: 'ddg_spice_search_code' is undefined

ddg_spice_search_code({"results":[{"name":"dateFromComponents:","namespace":"NSCalendar.dateFromComponents:","url":"http:///developer.apple.com/library/ios/documentation/Cocoa/Reference/Foundation/Classes/NSCalendar_Class/ReferenceNSCalendar.html#//apple_ref/occ/instm/NSCalendar/dateFromComponents:","description":"Returns a new NSDate object representing the absolute time calculated from given components. When there are insufficient components provided to completely specify an absolute time, a calendar uses default values of its choice. When there is inconsistent information, a calendar may ignore some of the components parameters or the method may return nil. Unnecessary components are ignored (for example, Day takes precedence over Weekday and Weekday ordinals). The following example shows how to use this method to create a date object to represent 14:10:00 on 6 January 1965, for a given calendar (gregorian). Note that some computations can take a relatively long time to perform. Available in iOS 2.0 and later.","synopsis":"(NSDate *)dateFromComponents:(NSDateComponents *)comps","type":"appleios","icon":"apple.ico","displayname":"Mac iOS Reference","modeltype":"function","rank":9}],"page":0,"total":"1","searchterm":"ios 6","query":"ios 6","matchterm":"ios 6","cleanterm":"","generalregex":"","regex":"","nextpage":1,"previouspage":null})

I haven't dug any deeper sorry. Might have a look tonight.

from zeroclickinfo-spice.

Odd I can't get it to trigger for me. Possibly Wiki gets its result faster to me because of my location.

from zeroclickinfo-spice.

Ah timing bugs... the worst kind.

Well it is triggering, but in my case it always is overruled by the wiki (which is correct BTW because its a better result).

The search ios 6 date however works fine https://duckduckgo.com/?q=ios+6+date although the top text overflows and it looks pretty awful...

The JavaScript error is possibly an issue though? I can repeat on IE9 (Chrome is fine however). Possibly a new bug?

from zeroclickinfo-spice.

Oh wow that top text does look bad. Thanks for showing me this. Would you mind making a GH issue for that other bug? I can look into it later.

Thanks @boyter!

from zeroclickinfo-spice.

No problem. One question though, whats a GH issue? Im missing some lingo here...

from zeroclickinfo-spice.

Oh sorry GitHub Issue. See the "New Issue" button top right?

from zeroclickinfo-spice.

Ah gotcha. Just wasn't aware GH was the short name :) Don't spend enough time here obviously :)

from zeroclickinfo-spice.