Open eric-laporte opened 8 months ago
Internally, an expression like trois:sienne
is converted into a graph:
Thus, the colon :
is interpreted as an instruction to call a sub-graph.
For the time being, you can type trois\:sienne
as a workaround.
Since this issue is directly related to the use of Locate with Regular Expressions rather than with Graphs, a future enhancement could involve automatically escaping colons before generating the graph representation.
A search query of the form a:b fails. The interface displays an error message suggesting the semicolon has been mistaken for a marker of subgraph call.
What steps will reproduce the problem?
What is the expected output?
A "Result info" dialog box should provide the number of occurrences found.
What do you see instead?
An error message is displayed in red: 'regexp: unexpected subgraph call in token_sequence_2_integer_sequence'. The search fails.
More info