Doc: add and fix docs for summary report subject line

[PartialShawn]

I added the subject line to the cli help response, and updated the code doc to use = for the parameter, and fixed where the quoting was.

The example uses unescaped spaces, which works fine for me. But the code says spaces must be escaped. I didn't fix this inconsistency, as you may want to go in a direction where one or the other is required. But as it seems to work with spaces, I'd recommend leaving it as allowing unescaped spaces.

Thanks for implimenting the subject line feature.

[PartialShawn]

Wait, I didn't check my last test. I'm not actually sure how to escape spaces anyway, so I guess the spaces comment should be removed?

[liuch]

As for the colon - you are right, it is my bad. Paired quotes can be used both ways, your version looks better.

[liuch]

Wait, I didn't check my last test. I'm not actually sure how to escape spaces anyway, so I guess the spaces comment should be removed?

As you see fit. You could create a new PR or add another commit.

[liuch]

The example uses unescaped spaces, which works fine for me. But the code says spaces must be escaped. I didn't fix this inconsistency, as you may want to go in a direction where one or the other is required. But as it seems to work with spaces, I'd recommend leaving it as allowing unescaped spaces.

I was sloppy and made an unfortunate point. I just meant that if there are spaces in the subject, you should either use quotation marks or escape them. The following uses are possible:

• subject=My\ cool\ report
• "subject=My cool report"
• subject="My cool report"

But this use is incorrect: subject=My cool report

[liuch]

Special HTML characters do not need to be encoded. Only special shell characters need to be escaped to ensure that the parameters are passed without distortion. The script will do the rest. That might be worth clarifying.