You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are the current problems with code in Markdown Preview in Brackets:
The background of code doesn't change. Just the font changes. This makes it harder to skim for code snippets.
Multi-line code preview is erratic. (Please look at the screenshot attached. The same <p> has different preview output.) The ``` doesn't disappear.
Sometimes the whitespace isn't preserved in multi-line code snippet.
Can the people who are developing this just conform to one Markdown standard so that I don't have to change my writing style just so the preview looks nice? Some people have advised me to remember the markdown format and not to depend on the preview. But I need the preview/final-render of markdown, while i look over my notes sometimes.
@Ativerc:
as for your issue No 2: the color of the code background within the preview panel depends on the theme chosen. Hence, some themes enforce a background color for the <pre><code>... elements and some other themes don't.
workaround in your case: edit and adapt the theme file of your choice...
Here are the current problems with
code
in Markdown Preview in Brackets:The background of
code
doesn't change. Just the font changes. This makes it harder to skim for code snippets.Multi-line code preview is erratic. (Please look at the screenshot attached. The same
<p>
has different preview output.) The ``` doesn't disappear.Sometimes the whitespace isn't preserved in multi-line
code
snippet.Can the people who are developing this just conform to one Markdown standard so that I don't have to change my writing style just so the preview looks nice? Some people have advised me to remember the markdown format and not to depend on the preview. But I need the preview/final-render of markdown, while i look over my notes sometimes.
P.S.: CommonMark.
The text was updated successfully, but these errors were encountered: