Be able to set the path where search

[guillaumeh]

Hello,

To add in wich list: Possibilty to set the path where search in repository. We have, in my compagny, a very big repository, and if we could set the path where search, it'll safe time ! :)

[Alec Thomas]

Is the exclude option not sufficient? eg.

[repo-search]
include = /some/path/*

[Heiko Graeber]

Replying to athomas:

Is the exclude option not sufficient? eg. include = /some/path/*

When I try to include/exclude a path like /trunk/... the plugin does not recognize the path. I had to write it without the leading slash: trunk/....

Maybe that's what caused the ticket to be issued. Wouldn't you think leading slashes should be allowed?

[Alec Thomas]

I'm pretty sure I just do a glob match, so it's likely that Trac's repository paths don't include the leading /. A note to that effect would be useful in the Wiki...

[Heiko Graeber]

I left a note in the Wiki.

[anonymous]

Heu... no, that's not sufficient.

My idear is to be able to set the path where search in the search form. For example, today, I want to search in /project1/ but tomorrow, I need to search in /project2/

And that the same for all of my team.

[anonymous]

1 month after, no news ? :)

[guillaumeh]

Help please ?

[Ryan J Ollos]

Reassigning ticket after changing maintainer of plugin.

[Ryan J Ollos]

Seems like we could probably just strip leading slashes from the include and exclude parameters. Since the original issue is solved in this ticket, I have opened another ticket to list this feature as an enhancement. See #6558.