Normalize code block indicators in README

[waldyrious]

• Remove space before the two colons, since most instances of the syntax used this format
• Add missing :: before the code block for the -S/--skip option

[DimitriPapadopoulos]

The space before :: is not just a question of format:

• foo. :: → foo.
• foo:: → foo:
• foo.:: → foo.:

We do not want .:: without a space, could you please change everything back to . :: with a space, or :: without a point.

See also #2596.

[waldyrious]

Thanks for the insightful comments, @DimitriPapadopoulos! I decided to use :: at the end of the line when the code block is related to that line, and to place the :: in its own line when the code block is unrelated to the previous line (in several cases they are related to the line below).

I've pushed a new commit with these changes. Please take a look and let me know what you think!

[DimitriPapadopoulos]

Looks good, more readable and easier to manitain this way. Thank you @waldyrious!

[waldyrious]

For convenience, here's the rendered version.

[jdufresne]

From the GitHub actions:

warning: check: Cannot analyze code. Pygments package not found. (line 30)

Might need to include pygments with the [dev] group to get the highlighting:

https://pypi.org/project/Pygments/

[waldyrious]

Might need to include pygments with the [dev] group to get the highlighting

How do I do that? Something related to this line in the codespell-private.yml GitHub actions definition file? Would it be sufficient to add Pygments to this list in pyproject.toml?

[waldyrious]

Would it be sufficient to add Pygments to this list in pyproject.toml?

Looks like it was :) I did that in 80a611a.

[larsoner]

Thanks @waldyrious !