[BUG] Automatically added CM comments output NULL marker

When using the Track Changes feature to edit a document, or when using the CM insertion commands, all of the commands and reactions to editing include a `(null)` value in the output. For example, in using the **Format ▸ Insert CriticMarkup Comment** command, we get the following:

 {>>(null) - 2019-06-05 12:26:08<<}

In investigating why or what that data was meant to be, I came across the "Insert automatic comment with CriticMarkup" setting, which by default is enabled, but has an empty value for the subordinate "Comment" option. Once I added the word 'test' to this field, then I got a sensible result:

 {>>test - 2019-06-05 12:26:08<<}

In checking Composer, it looks like this condition is handled more gracefully. However I would suggest that if the "Comment" field is empty that there only be one space added between the " - " delimiter and the cursor. Here is how Composer prints:

 {>>  - 2019-06-05 12:26:08<<}

And here is the suggestion:

 {>> - 2019-06-05 12:26:08<<}

[BUG] Automatically added CM comments output NULL marker

Comments

Didn't find what you were looking for?