If I include a file in my Org file, say using #+INCLUDE: "script.sh" src sh and export to HTML, the included file shows up as a <pre> block, which is nice. However, a leading comma is put in front of every line that starts with a #, even those with leading whitespace. I understand that a comma is used to escape # in the first column of literal examples, to distinguish from Org comment lines. (This escaping is no longer strictly necessary, since the #+BEGIN_EXAMPLE block can now be indented.) For included files, could we not add the escaping commas? Thanks for considering! -- Best, Hsiu-Khuern.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4