if you have leading wildcard enabled (which in latest opengrok is by
default)
then you can do:
*multispan*
tokens which are matched are usually separated by whitespace/language
dependent chars for identifiers and lucene query engine doesn't do
wildcard searches by default
(e.g.
"param_warning keyword_multispan_iterator::resolve_issue() {"
would be these tokens: param_warning , keyword_multispan_iterator,
resolve_issue )
for more about supported query syntax refer to help button (e.g.
http://src.opensolaris.org/source/help.jsp - this help is a bit dated,
we will probably need to update it to reflex latest lucene / default
states of switches - most probably once we upgrade to lucene 4.0 I will
do it, if someone doesn't beat me to it (do I hear volunteer? :) ) )
hmm?
L
On 31.7.2012 2:12, Xiao, Ze Lin wrote:
A user of my OpenGrok deployment is performing a full search on a
project with query: "multispan"
The results of this search show these following instances:
* "* keyword-multispan API when needed"
* "* @api keyword-multidelete"
* "ret = some_function_create(p1, "keyword-multispan");
* "* return all the errors if the caller is keyword-multispan"
* "table keyword_multispan 'Example multispan" { user
server-processed } {"
* "get = keyword-multispan {"
However, there is definitely an instance of "multispan" that isn't
showing up in the results, which is:
* "param_warning keyword_multispan_iterator::resolve_issue() {"
Since this instance of multispan isn't the end of a word, I've
tried "multispan*" as well to no avail. Is there a better way to
search for ALL instances of "multispan" in this case?
Thanks,
Ze
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
_______________________________________________
opengrok-discuss mailing list
opengrok-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
