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
Preview during edit/create seems to render monospace content wrong when tabs are involved. Here is an example post: https://www.biostars.org/p/490053/
This is probably owing to how tabs are handled - vep<TAB><SPACE> might take up the same white space as <TAB><SPACE> if the tab just jumps to end of word. But if every <TAB> were being translated to 4/8/whatever <SPACE>s, the text would render differently. I personally prefer spaces for this reason, but the point is, preview and real display should handle <TAB>s the same way. This inconsistency breaks display in these cases. Can something be done about this or is it up to the markdown engine creators?
Preview during edit/create seems to render monospace content wrong when tabs are involved. Here is an example post: https://www.biostars.org/p/490053/
This is probably owing to how tabs are handled -
vep<TAB><SPACE>
might take up the same white space as<TAB><SPACE>
if the tab just jumps to end of word. But if every<TAB>
were being translated to 4/8/whatever<SPACE>
s, the text would render differently. I personally prefer spaces for this reason, but the point is, preview and real display should handle<TAB>
s the same way. This inconsistency breaks display in these cases. Can something be done about this or is it up to the markdown engine creators?Same content as the post but here:
With tabs:
Here's what that looks like:
Cleanup, tabs replaced with spaces:
Here's the
cat -A
of the above block:As you can see, GitHub flavored markdown handled both beautifully.
The text was updated successfully, but these errors were encountered: