User talk:Bluebirch

Issue Tracker
Thanks for your work, looks great! I just fixed the id commands. --Jorges 23:35, 3 March 2009 (UTC)


 * Glad you like it and thanks for the help! Sorry, that I forgot the testing phase... serchilos regexes aren't as powerful as I thought. Well, the reason I used a regexs was that bug ids are often written as #99999 however in the URL the # gets escaped to %2399999 which is confusing. The other reason was that I wanted the i to be optional (maybe I should have left it away altogether) so dbug #518166 (or dbug 518166) is the same as dbugi #518166. As this is never a valid package name there is no problem. --bluebirch 19:21, 4 March 2009 (UTC)


 * The escaping of # to %23 happens because otherwhise the URL argument would be stopped and the rest would be read as a name of an anchor.
 * In my opinion a system of two keywords "fooi {id}" and "foo {package/product}" (and fooq of course) without any # alternative would be the easiest to understand and remember. Because since typing "fooi 123" or "foo #123" is the same number of keystrokes. But I leave that up to the actual users of the command. --Jorges 21:56, 4 March 2009 (UTC)


 * I think "foo 123" is the simplest (no "i" AND no "#"). Less commands seems easier to remember. The reason "foo #123" (or "fooi #123") is nice to have is that the bug id is often written in mails or apt-listbugs with the "#" and so it is quicker to copy+paste #123. This works for "dbug {id}" but for unknown reasons it isn't for "ubug {id}". I don't known why "dbug 123" is matched with "dbug {id}" but "ubug 123" is matched with "ubug {package}". Until solved the "i" is needed. --bluebirch 22:13, 4 March 2009 (UTC)


 * Actually it turns out "dbug 123" was matched to "dbug {package}", too (but debian checks if it is an id or package by itself). The reason seems to be that serchilo prefers simple commands over regexes. --bluebirch 22:32, 4 March 2009 (UTC)