Formatting LBRY comments
Styling can make a comment easier to read and easier look to at at a glance (skimming).
Bold and italics
Bold and italics in LBRY comments works similarly to how Markdown works:
An LBRY comment can be styled in *both italics* and **bold**.
An LBRY comment can be styled in both italics and bold.
Bold and italics do work at the same time, but bold is so nondistinct that it is difficult to see the difference. In fact, bold is almost worthless.
Unlike on YouTube, space does not work for indentation (this is like in raw HTML). Instead, use HTML non-breaking space:
This is *indented* text.
This is indented text.
Note 1: On 2020-10-24 the formatting of comments with space indent changed (but using ‘nbsp’, as described here, works fine). It now seems to format it as code if there are over a certain number of spaces.
Note 2: LBRY now fights any attempt to use empty lines. It is currently not known how this can be defeated.
Links work in LBRY comments like in Markdown:
Douglas Crockford says *"[No more tabs!](https://www.youtube.com/watch?v=MBWAP_8zxaM&t=9m37s)"*.
Douglas Crockford says “No more tabs!“.
Note that https:// is required. Otherwise, it will not render as a link.
Like in Markdown, backticks (
`) works for code formatting. But in contrast to Markdown, <pre></pre> does not work.
In Bash, the environment variable `PS1` controls the prompt.
In Bash, the environment variable
PS1 controls the prompt.
Unlike Markdown, a hard newline will result not just in the following text starting on a new line, but an empty line! Thus the Markdown-like source will not look like the output. For example, an empty line in the source will result in two empty lines…