Mat wrote: > > > We'd get infinite options if one could use §1, §2, ... >
That sounds like a shift away from "Markdown Like" ... In that the character pair is "code for something" ... one might argue that "<<< ...<<<" is already not that Markdown Like. Its an interesting question. In earlier discussions with TonyM using a "universal prefix" came up. Extending on that idea, for instance starting a line with a full-stop, or whatever ... .§ = activate Mat style Custom Wikitext pragma for "§" .d = activate screenplay Dialogue styling These approaches remain nicely compact but are not ideal "Markdown Like"--plain text readability is not brilliant. That said, once you use up available characters with meaning its a viable alternative. Another approach it to add NO EXPLICIT MARKUP AT ALL but construct a pragma that via regex analyses pattern of text in line. That works easily for highly structured texts. For instance any line of a "transition" in a script (like "CUT TO:" or "FADE OUT:") are easily identified by pattern without adding any markup & can be styled appropriately. The text in these cases is "its own markup". I often wonder if that "silent" approach could be extended to more conventional text. It would be useful if TW could work as a custom markup > constructor+interpretator. (Possibly the character should trigger more than mere CSS. I would guess > pipe characters, when creating wikitext tables, do this, right? In that > case, § could trigger some user defined *macro*, perhaps titled § ...or > §1, §2... to operate on the text snippet in question.) > I'm not so sure about extending this into basically a command parser :-) . If you going pragma route then its possible, but focus on simple insertion of styled elements is quite a lot to get working well for one pragma already. How many many pragma were you thinking of? :-) I do think a "kitchen sink" pragma (i.e. does a bunch of different things at once) is probably not a good idea. On this, extending beyond element styling, to "interpret activity insertion" some use cases are needed to think with. My further thoughts TT -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/2f72ba6d-34e6-4bd4-bba3-bec1d039aebdo%40googlegroups.com.
