With some very minor changes to $:/plugins/tiddlywiki/highlight/highlightblock.js and plugins\tiddlywiki\highlight\files\tiddlywiki.files i got highlight.js working statically in nodejs
Ticket for this here: https://github.com/Jermolene/TiddlyWiki5/issues/1301 and an example of it working here https://dl.dropboxusercontent.com/u/41230376/blogtest/hljs/HLJS.html On Wednesday, 31 December 2014 22:33:55 UTC+9, Jim Lehmer wrote: > > On Sunday, December 21, 2014 1:24:27 PM UTC-6, James Anderson wrote: >> >> >One way to fix it might be to make the rendertiddlers command accept >> multiple runs of arguments: >> >> I understand the rational :) I guess that because I wanted to run two >> separate filters using two separate static templates it wasn't really a >> considered use case. I wouldn't mind an option on rendertiddlers which >> signals whether or not to delete the folder's contents. To me having a very >> long list of filters and templates after rendertiddlers seems a little >> difficult to read. >> > > I concur. Right now that's exactly how I am generating my static site - > with a *rendertiddlers* at the start and then a long set of additional > *savetiddler > *and *rendertiddler *commands to output fixed assets. Would be easier if > *rendertiddlers > *supported some sort of "clean" parameter (thinking *make clean *here) > that indicated whether to delete the contents of the output directory. > Would probably need to have clean be the default to mimic current behavior > for backwards compatibility but as long as we could do something like > *clean=no > *or *noclean, *that would be fine with me. > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
