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
Don't want to go into the whole religious debate of spaces vs tabs, but some people do use tabs for their scss source code, and currently that causes the presentation of said source code that is included in an item's header section, to come out wrong.
I think the code_block macro defined in utility.macros.njk can do a bit more work to accommodate the tabs-crowd in producing properly formatted source presentation, by consistently converting tabs to two spaces.
Could be as simple as using the replace filter when rendering the content property, i.e. ,
{{ content|replace("\t", " ")|escape|safe }}
The text was updated successfully, but these errors were encountered:
* master:
Upgrade deps (notably webpack4).
Include dist/ in repo so that package can be run from repo.
Fix bug if annotations try to access missing `env.herman` [fixes#273]
Fix bug displaying tabs in `<code>` blocks [fixes#271]
Don't want to go into the whole religious debate of spaces vs tabs, but some people do use tabs for their scss source code, and currently that causes the presentation of said source code that is included in an item's header section, to come out wrong.
I think the
code_block
macro defined inutility.macros.njk
can do a bit more work to accommodate the tabs-crowd in producing properly formatted source presentation, by consistently converting tabs to two spaces.Could be as simple as using the replace filter when rendering the content property, i.e. ,
The text was updated successfully, but these errors were encountered: