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
I've experienced an issue with org-mode file rendering on Codeberg and I found that they use your library for writing out HTML from Org files. The issue is that when one has a code block like this in an Org file:
Notice that there seems to be a blank line above the line guix pull but not after it, making the padding of the code block look strange. You can see a real-world example of this issue here:
Is there any way you could trim empty lines before and after the actual content of a begin_src block while still retaining any indentation in lines that contain real content? I think that would help make code block rendering look more consistent for a wider variety of Org files.
It appears that blocks.org does not have any examples with spacing like this, so it seems to be an untested scenario.
Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hi all!
I've experienced an issue with org-mode file rendering on Codeberg and I found that they use your library for writing out HTML from Org files. The issue is that when one has a code block like this in an Org file:
The output looks like this on your demo site:
Notice that there seems to be a blank line above the line
guix pull
but not after it, making the padding of the code block look strange. You can see a real-world example of this issue here:https://codeberg.org/SystemCrafters/crafted-guix#headline-3
Is there any way you could trim empty lines before and after the actual content of a
begin_src
block while still retaining any indentation in lines that contain real content? I think that would help make code block rendering look more consistent for a wider variety of Org files.It appears that blocks.org does not have any examples with spacing like this, so it seems to be an untested scenario.
Thanks a lot!
The text was updated successfully, but these errors were encountered: