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
Yeah I was under the same impression about jade filters when trying to call template data from :coffeescript in docpad. Strangely enough using the buffering or iteration inline code (- or = or !=) all work. Also I fail to see the problem with markdown: except the obscure double space line ending to create a break, everything else is working just fine and from that last link Delapouite posted above here I conclude jade's internal rendering tries up to 4 different engines/packages before it surrenders and tells you to install one. Having docpad-plugin-marked makes docpad-plugin-jade use that one possibly (no idea) but I have globally installed most important stuff including 'jade' and 'marked' packages (not the plugins) which could make the difference.
Is there a simple way to attach marked from its plugin to the Jade's plugin, so we could use the
:markdown
filter there?The text was updated successfully, but these errors were encountered: