Serchilo:Bugs
From Serchilo
Fixed bugs in archive.
[edit] Can't remove bad page. (done)
I added a new command, but there is no command attached to the page, only an explanation, I looked for a way to delete it but couldn't find one.
http://wiki.serchilo.net/Chewbone_Mp3blog_Search
I added another page that works and I want to keep it:
http://wiki.serchilo.net/Chewbone_Mp3_Blog_Search
- Only sysops may remove pages. But your redirect is also a good solution. --Jorges 13:04, 13 May 2008 (UTC)
[edit] Tagesschau kollidiert mit UNIX Timestamp
Beide Kommandos benutzen ts. Timestamp war aber zuerst da!
- OK, dann schlag vor, was wir machen sollen! :) Ich selber benutze keines der Kommandos, mir ist es egal. Laut Statistik wurde in den letzten 30 Tagen damit 6x die Tagesschau und 10x die Timestamp angesteuert. (Ja, ich hab vor, demnächst regelmäßig Statistiken zu veröffentlichen.) --Jorges 16:03, 23 October 2008 (UTC)
- Statistiken wären super! Die wären eine große Entscheidungshilfe bei Konflikten. --Kevang 23:35, 12 July 2009 (UTC)
[edit] Default Command doesn't work is rather bad documented
I really like Searchilo, but it disturbs me when it doesn't "google" stuff automatically. I've set up the default command in my preferences page. It is set to "g" but I've tried "g " as well (not the leading space). Also, personal commands don't work. Thus I suspect the error somewhere in my configuration. But where? Firefox should send the cookie I am authenticated with. Maybe I'll sniff my HTTP connection to check whether Searchilo (besides the wiki) can know about me at all. I've installed that search thing for firefox that replaces my google search. I did this, however, before I set the default command. What do I have to do to get the default command thing working? --Muelli 02:02, 25 December 2008 (UTC)
- Okay, I resolved this issue. After I found out, that I have to use "muelli.serchilo.net" (which isn't very obvious) to use User Commands, I managed to install the firefox search plugin that uses my domain. Default Command works perfectly now.
I propose to make perfectly clear, i.e. in that preferences dialog, that you have to use *your user sub-domain* (i.e. http://example.serchilo.net) in order to use the default command and user commands in general. --Muelli 02:32, 25 December 2008 (UTC)
- Thanks for your suggestion. There is now an info on Special:Preferences->Serchilo about user commands. Hopefully, this is clear enough. Besides, there is this Serchilo:User commands. --Jorges
[edit] regex commands should be prefered over keyword commands (done)
Regex commands are used to restrict valid input (e.g. only numbers). So a keyword command can function as a default match. However it seems that serchilo currently uses the keyword command if a regex command and a keyword command match. An example is on my user page. The commands mybug and mzbug are identical. The only difference is that "mzbug {package}" is implemented via keyword and "mybug {package}" is implemented via regex ("m?bug {id}" are both regex commands). However the search "mzbug 1" is matched by "mzbug {package}" (because it is keyword command) and "mybug 1" is matched by "mybug {id}" (because both are regex commands and {id} is defined first).
It seems the proper behaviour would be that regex commands be matched (it would be equally good if the first defined would be matched -- independent of how it is implemented) before keyword commands, so in both cases "m?bug 1" would match {id}. --bluebirch 08:24, 5 March 2009 (UTC)
- Regex command are not only used for restricting input but also for defining a set of keywords, see for example Google Web Pages in certain language. This matches any keyword starting with g followed by two chars. And now there are also two keyword commands, guk and gch. These must be preferred over the regex command or they won't get called at all.
- To achieve your desired behavior, you can define both commands as a regex command and put the preferred one before the other one - as you did with mybugi and mybug. --Jorges 03:20, 8 March 2009 (UTC)
- I didn't think of that. It could be solved by setting priority in three groups (no syntax changes), but I don't think it would be worth it. Thank you for explaining. --bluebirch 12:44, 8 March 2009 (UTC)
[edit] Regulärer Ausdruck wird gefunden, aber nicht richtig ersetzt
Beispiel: http://en.serchilo.net/WDE%20Test - Anhand der case-insensitiven Suche in der Datenbank wird zwar das Kommando gefunden, die Ersetzung der Argumente funktioniert jedoch nicht, vermutlich, weil es dann nicht case-insensitiv ist. Am besten sollte auch die Suche in der Datenbank case-sensitiv sein (BINARY?) oder beides case-insensitive. --Stefan
[edit] Overloading of keywords across namespaces
It appears that queries are resolved to commands first by namespace, then by the number of arguments. It should be the other way round. For example, I have defined a user command la with no arguments that takes me to the course page of my old Linguistic Annotation class. Now I can't use the Latin dictionary command la with one argument (except by prefixing it with some command space different from my personal one, see my forthcoming feature request)! --Kevang 23:47, 12 July 2009 (UTC)
[edit] arxiv beherrscht keine Leerzeichen
Zum Beispiel liefert die Suche nach "arxiv two words" die (fahlerhafte) Adresse http://arxiv.org/find/all/1/all:+two%20words/0/1/0/all/0/1, wobei http://arxiv.org/find/all/1/all:+AND+two+words/0/1/0/all/0/1 zu einem richtigen Ergebnis geführt hätte. Auch bei Ausdrücken in Anführungszeichen (-> EXACT) schlägt die Suche fehl. Ich habe allerdings keine Ahnung wie und ob das Problem mit der hier unterstützten Syntax für beliebig viele Suchbegriffe korrigierbar ist...Pond247 23:13, 1 March 2010 (UTC)
