Two patches that adds a '-l', '--showurl' option to search (and namedcmd) that will show the bugid as a url pointing to the bug for copy/paste into a browser.
Created attachment 130059 [details] pybugz-0.7.0-bugurl.patch pybugz-0.7.0-bugurl.patch
Created attachment 130061 [details] pybugz-0.7.0-namedcmd_bugurl.patch pybugz-0.7.0-namedcmd_bugurl.patch
Can you please also update this for 0.7.2? Thanks much, William
Created attachment 139582 [details, diff] New version for 0.7.2
Created attachment 139584 [details, diff] pybugz-0.7.2-namedcmd_bugurl.patch How about adding these to the program? :)
Comment on attachment 139584 [details, diff] pybugz-0.7.2-namedcmd_bugurl.patch For the namedcmd patch see bug #191137
Hello, I am now up and working with pybugz again, so can you do me a favor? We are now using github, so can you please check out the latest source from there and write this patch against the master branch and re-attach it to this bug? The clone url is git://github.com/ColdWind/pybugz Thanks much, William
Please re-open this when you get a chance to rewrite the patch against the master branch at git://github.com/ColdWind/pybugz.git. Thanks much. William
Created attachment 186881 [details, diff] Updated patch Updated patch against git (commit fb26ce3d99abf71bd60bb1c5c363adb1071b8bf0)
New patch attached
I am unable to apply your patch against my repository by doing the following: cd pybugz-repo patch < pybugz-bugurl.patch The patch program is unable to find the file that it should patch. Also, I don't understand part of the patch (mainly probably because I am still learning python), but why do we have to touch bugzilla.py for this patch? It seems to be something that only affects the cli which is in bugz/cli.py. Thanks, William
(In reply to comment #11) > I am unable to apply your patch against my repository by doing the > following: > > cd pybugz-repo > patch < pybugz-bugurl.patch Should be: patch -p1 < pybugz-bugurl.patch (git adds a virtual topdirectory to the patch path when extracting a patch) > Also, I don't understand part of the patch (mainly probably because I am > still learning python), but why do we have to touch bugzilla.py for this > patch? It seems to be something that only affects the cli which is in > bugz/cli.py. I touch bugzilla.py because it was the easiest way to get the new option to search working. bugzilla.py is called with **kwds, ie with all options that search got. The other way would have been to filter out showlink from kwds prior to calling bugzilla. /Regards Togge
How difficult would it be to filter out showlink instead of passing it on to the bugzilla interface since it isn't used at that level anyway? Thanks, William
Another way you can submit the patch that would work really well is to use git format-patch. This will create a patch, with authorship information, etc, which I can directly commit to the repository. For information on this, do the following: git help format-patch or git format-patch --help Thanks, William
Created attachment 187109 [details, diff] Patch against git Updated patch to keep bugzilla.py clean. Diff with git format-patch origin /Togge
I have added this to 0.7.4_rc3; however, I made a couple of slight changes to the original patch. First, the command line option is --show-url instead of showlink. To me that is more clear since the url itself cannot be clicked on to open a browser, and you would be able to click on a link. Also, I did not include the title wrapping at this point, since I found that listbugs needed to be cleaned up another area. Now there is only one print statement at the bottom of the for loop. Please open another bug regarding wrapping the output and provide a patch for listbugs if you can. Thanks for your report. William
