Stephanie Evert

Admittedly, I just had to fix this in CWB/Perl, which did indeed hang, too … The proper string to send to CQP is "$cmd\n;\n.EOL.\n"

Enhance CWB::CQP interface so that a CQP command truncated by a comment doesn't hang anymore.

As for the proposed enhancement (not bugfix!), this would break backwards compatibility. Comments in mutliline CQP commands have been allowed for decades, so it would be unacceptable to disable them now. As a start, this would break the first example in Sec 6.4 of the CQP User Manual. I would argue that no such enhancement is needed: End users can simply complete the command on the following line (but would hopefully use readline mode anyway). It's the same as the continuation prompt for an incomplete...

This is not a bug, CQP behaves as intended (I refrain from writing “documented” since we don't have a precise specification of the query language). In normal mode, a CQP command can span multiple lines until the terminating semicolon is encountered, and each of these lines can include a comment. So the example [pos="JJ.?]? ("#?brexit"%c) is parsed as [pos="JJ.?]? (", i.e. an incomplete command. It is correct behaviour for CQP to wait for additional input until a semicolon or parse error is encountered....

Fix spurious test error in Perl CWB package

Enhance ucs-print (via UCS::DS::Format) to auto-detect UTF-8 strings and align columns accordingly

Remove debugging code from ucs-config (doh)

- improve ucs-tool to enable command-line completion (and display script path)