It is possible, but is an enhancement of bhsearch. We could extend whoosh query parser to detect which tokens are actually TracLinks, use trac formatter to resolve them to resource urls and then parse those urls to extract the object we are interested in.
If it is a priority, it can be done, but IMO, there are currently many other areas that require our attention. I have created a ticket[1] for this. If this is important, we can raise its priority and I can have a look at it. [1] https://issues.apache.org/bloodhound/ticket/538#ticket On Thu, May 30, 2013 at 10:24 AM, Gary Martin <[email protected]> wrote: > > > Olemis Lang <[email protected]> wrote: > >>On 5/30/13, Anze Staric <[email protected]> wrote: >>> Let me clarify, I have a Ticket instance and need to generate all >>> possible TracLinks, that would, when used in a wiki page, resolve to >>> the url pointing to the ticket that I started with. If this is >>> possible with the formatter you mentioned, could you point me to the >>> module where it is located, so I can check it out? >>> >> >>No, no ... I misunderstood your intentions . I thought you were trying >>to do the opposite . IMHO what you'd like to achieve is impossible in >>theory ; at least not without introducing a lot of extra code ... or >>reducing problem scope to a well-known set of TracLinks providers . > > For the purposes of searching, I would have thought you would only need to > know what the object is rather than what the possible representations are. > > Cheers, > Gary
