Re: Package Abstracts

On Thu, 18 Nov 2004 21:42:34 +0000, Helgi Þormar <helgi@trance.is> wrote: > On Thu, 2004-11-18 at 21:21, Paul M Jones wrote: > > Hi Paul > > > > > >>The Bug link thing is even easier thank you think. One example is to > > >>treat the word "Bug" as an interwiki keyword. In the Yawp.conf.php > > >>file, you would add: > > >> > > >>[yawiki] > > >>interwiki_site = Bug, > > >>http://pear.php.net/bugs/bug.php?id=%s > > >> > > >>Then Text_Wiki will automatically translate the text "Bug:2228" as a > > >>link to http://pear.php.net/bugs/bug.php?id=2228 > > >>-- no programming > > >>involved, just a change to the config file. :-) > > > > > > > > > I see, never was sure what those interwiki things were anyway :) > > > > Heh. :-) The idea is that you can define the names of other wikis and > > then be able to link to them without using the full URL; the > > word-plus-colon indicates the wiki name, and the part after the colon > > indicates the page. As a bonus, it turns out this marking is useful for > > all sorts of non-wiki things that can be represented as URLs: file > > links, bug links, links to "normal" sites, and so on. > > > > > > > but can it do like something similar to this, #4353, and not changing > > > #foo into a link, i.e. kinda yes just allowing numbers through that > > > config ? > > > > I think hash (pound) sign is too generic for that particular use. > > Text_Wiki already uses # in a few different ways: > > > > Using ##red|double hash marks## indicates colored text, > > > > # at the beginning of a line indicates a numbered list item, > > > > If you have [#anchorname] it's a link to an anchor on the same page, > > > > And [[# anchorname Displayed Text]] creates an anchor on the page. > > > > So adding #1234 as a link to bugs is probably not useful in this case, > > especially as # might well be used to number non-bug things. Having > > "Bug:1234" would be both obvious to the reader, and easier to implement > > (otherwise we'd need a new "bug.php" rule to look for numeric-only hash > > marks, plus corresponding rendering rules, blah blah blah). > > > > I hope that makes sense. > > Well here's the problem, more often then not, people point to a > bug/feature request by saying "Look at #454", I've seen this in more > then just PEAR and more then just PHP, so I've become to look at this a > kinda standard, of course most useful is to just do bug:34 ticket:34 or > so, which btw. should also be supported :) I anyway would like to see > #443 also supported since to me it's kinda wide spread for pointing to a > bug report, and I of course am a ware of that #005500 or so could be > turned into a bug report link, when the person meant a hex, but > sometimes you can't have everything, can you :) > > So I'd like to see #43534 supported, we did that with a simple and clean > preg_match for the changelogs in PEARweb, and even made it support Bug: > 453 to be converted into link in just a one liner regex :) > > Coming to think about it, on the wiki it self this is less important, > having this on the changelog was of course the most important :) > > It's your call really. > I would rather Bug #123 and Bug:123 be supported. Changing #123 to a bug link is just too prone to error. I could easily see someone saying "line #123". -- Justin Patrin