Document undocumented indent(1) options badp/nbadp, bs/nbs, and lc.

[pfg]

Summary

Improve manpage for indent(1)

Change from Piotr Stefaniak:
https://github.com/pstef/freebsd_indent/commit/a6652c3f330e26cd96c4ed337905b2ca4c42e64b

[bcr]

A few corrections. Running textproc/igor and mandoc -Tlint will find errors in man pages like this.

usr.bin/indent/indent.1

153 ↗

(On Diff #22657)

You need a line break after the sentence stop here.

195 ↗

(On Diff #22657)

Another line break here.

340 ↗

(On Diff #22657)

Another... well, you guessed it. ;-)

[pfg]

Use a newline when finishing a sentence.

[pfg]

Done, thanks!

usr.bin/indent/indent.1

151 ↗

(On Diff #22657)

I am wondering, is it OK to start a line with a comma? Perhaps this comma is also reduntant.

[bjk]

usr.bin/indent/indent.1

151 ↗

(On Diff #22657)

Generally the comma would go on the previous line, with a space between "bad" and the comma. I forget whether the version as-committed will end up rendering with a space before the comma. You're also right that this particular comma is not strictly needed.

[wblock]

usr.bin/indent/indent.1

151 ↗

(On Diff #22657)

When spoken, it doesn't quite sound right without the pause represented by the comma.

To render correctly, the comma needs to be on the same line as the .Fl macro:

.Fl bad ,

The space before the comma there is a delimiter to the macro. It renders the "bad" as the flag, then adds the comma without a space: bad,

It's hard to think of any time a line beginning with a comma with be rendered correctly.