Mat, FYI, this is something I mentioned quite often, but probably was misunderstood :-) ...
BJ provides more than one solution to parse in TW. Either through potential new content type parser sets, or through a pre-parser that runs before the main TW parsers. IMO this is simply a pragmatic issue. The major barrier being that the main parsers are in JS which is not transparent to most of us. In other words, the barriers are more to do with how it would need coding than any intrinsic issue in TW. Nothing, as far as I can see, is stopping it. For myself, I used BJ's raw regular expressions based pre-parser that is easy to use (for me being into regex) and serves my needs well to produce customised wikitext. Ask if you need more info. Best wishes, Josiah On Sunday, 29 December 2019 16:14:57 UTC+1, Mat wrote: > > Please help me phrase this into something suitable for a gh request - or, > for that matter, enlighten me as to why I shouldn't: > > > Several requests over the years concern how some little thing should parse > (term?) in some special way, equivalent to how e.g * and | become bullet > lists and tables. (My own latest wish is for tab spaces > <https://github.com/Jermolene/TiddlyWiki5/issues/4398>). The purpose is > to minimize distractions from your train-of-thoughts when authoring stuff. > > I believe Jeremy has expressed positive comments about having a generic > solution for this but I don't think there is a github issue about it nor do > I think there has been any serious discussion about it. So, what is needed > for this? As noted, it would possibly solve several made requests and it > would overall be a powerful addition to the dynamism of TW and wikitext. > > What would it take to implement this? > > <:-) > > > > -- 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/b4513b2e-e35a-495a-917d-13c3d12399eb%40googlegroups.com.
