It’s worth also mentioning the `\rules` pragma which can be used at the top of a wikitext tiddler to limit the parse rules that are recognised during parsing.
Most of the core stylesheets are typed wikitext but include the following at the top to suppress all wikitext formatting except transclusions and macro calls and definitions: \rules only filteredtranscludeinline transcludeinline macrodef macrocallinline macrocallblock Best wishes Jeremy. > On 29 Apr 2016, at 13:44, Devin Weaver <[email protected]> wrote: > > > > On Friday, April 29, 2016 at 6:24:56 AM UTC-4, [email protected] wrote: > I was hoping there would be an alternate to changing the type of the tiddler > to text/vnd.tiddlywiki because that messes up some stuff. > > Like what specifically? Rendering? Here is what I do in my TiddlyWikis: > > If the style sheet has no macros then I use text/css if it does use macros > (like <<colour>> or <<datauri>>) then I use type text/vnd.tiddlywiki and wrap > the whole tiddler in a <pre> tag so it renders nicely. I could also use the > three back ticks to code highlight if I had the highlight plugin. Since the > inclusion of CSS seems to ignore HTML surrounding it: > > title: MySpecialStyle > tags: $:/tags/Stylesheet > type: text/vnd.tiddlywiki > > \define border-radius(size) > border-radius: $size$; > -moz-border-radius: $size$; > -webkit-border-radius: $size$; > -o-border-radius: $size$; > \end > > <pre> > .foobar { > <<border-radius 6px>> > color: <<colour foreground>>; > background-color: <<colour background>>; > } > </pre> > > Eventually I realized the only time I needed to see the style was while > editing and that had no formatting so I dropped the <pre> tags all together. > And to be honest this makes sense. I would want my application/javascript to > be interpreted with the wikitext parser (gods, one left shift bit opperation > and all hell would break loos (var x = y << 1; // => BOOM!) Or in a text/css > if you has an empty string it would think you meant bold: > > .foobar { > content: ''; > } > .bar { > content: ''; > } > > Would expand to: > > .foobar { > content: <b>; > } > .bar { > content: </b>; > } > > And that would be silly. > > So there are reasons that macros are only parsed in text/vnd.tiddlywiki and > not in alternative types (gosh think about parsing wikitext out of an > image/jpg). > > > > > > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywiki > <https://groups.google.com/group/tiddlywiki>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/465873e8-8ffb-4a02-beba-ce7a9ed61452%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywiki/465873e8-8ffb-4a02-beba-ce7a9ed61452%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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 https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/7FDDFF6D-E272-42B5-B187-D4F54B209084%40gmail.com. For more options, visit https://groups.google.com/d/optout.
