> > As far as I can tell, this doesn't require a 'bts list' command, > > although I agree that we both want the same final outcome. > > > > More specifically, 'bts show/bugs' (or list) could simply display bug > > lists/info to the console a la reportbug, as you put it. > > indeed, my first idea was to use a particular $BROWSER that would simply parse > the html and show the list (thus "bts list" and not a commandline option)
As argued above, it is silly for us to create a custom $BROWSER when one already exists in the reportbug code. The reason I am suggesting a command line or configuration option is because it seems inconsistant to me for 'bts show' to use a web browser, and 'bts list' to use the console. I would prefer a single set of semantics, that could in turn be configured to use either the web browser or the console. For that matter, as previously indicated, I think that a console bug interaction tool, such as that built into reportbug, is far more usable than viewing the bugs webpage using a text browser. Charles -- Golfers! If fewer strokes Are what you crave You're out of the rough With Burma-Shave http://burma-shave.org/jingles/1931/golfers
signature.asc
Description: Digital signature
