You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure this makes sense, but afaict the tree from -T/-tree shows the matched input in a tree structure, but not the result of applying any tag changes and such. Would it be possible to show these in the parse tree? E.g. instead of just
(This idea brought to you by half an hour of debugging why %2[defnes=ind] did not seem to apply because I thought parse trees showed the output values.)
The text was updated successfully, but these errors were encountered:
The main difficulty is that by the time the output values are known, the tree structure no longer exists, since those output values are produced precisely by disassembling the tree.
On the other hand, it wouldn't be that hard to store the string-ified versions of nodes around rule application and thus produce a tree fairly easily by piping debug output into a python script of some sort.
I'm not sure this makes sense, but afaict the tree from
-T/-tree
shows the matched input in a tree structure, but not the result of applying any tag changes and such. Would it be possible to show these in the parse tree? E.g. instead of justone could have
(This idea brought to you by half an hour of debugging why
%2[defnes=ind]
did not seem to apply because I thought parse trees showed the output values.)The text was updated successfully, but these errors were encountered: