Thanks for chiming in, Mario. Sorry I didn't get a chance to respond the other day, but here's what I'm thinking:
On Thursday, February 4, 2016 at 9:11:57 AM UTC-5, PMario wrote: Didn't you see my proposal, using: ---space which works perfectly fine and > seems to be consistent too. > It's *definitely* a good workaround, as is the idea of a custom <hr />. The inconsistency isn't slowing me *personally* down in my use of TiddlyWiki; I just think it's worth discussing whether the reuse of the string *---* to accomplish two wholly different aims in TiddlyWiki (*—* and *<hr/>*) adds an unnecessary layer of potential confusion for new users. It seems like a very manageable, though completely unnecessary, quirk of TW's wikitext. > If I read the dash wikipedia page at: see: > https://en.wikipedia.org/wiki/Dash, I have to say: "You are using it > wrong". ... The mdash is not meant to be used as a short <hr>. So why > change the TW syntax to add an edge case, as default behaviour. > I'd argue the replacement syntax I'm suggesting is *logically better*, with *---* wikified uniformly regardless of the context in which it's used. While its true the m-dash isn't intended as a demarcator, we can reasonable expect end users to engage some non-standard behavior. Programmers use all sorts of punctuation marks "wrong," for example. ;) I see two opportunities for consensus or disagreement here: 1. Whether using two different strings (*---* and *----*) as wikitext shorthand for *—* and *<hr/>* is better than using one string (*---*) dependent on context (on its own line or not). - I'm a firm *yes* on this one. If Jeremy were only now sussing out the spec for TW wikitext, I could campaign on this point with no hesitation. (I hate I missed the chance earlier in TW5's development.) 2. Whether it's worth risking backward-compatibility problems at this late date to refactor the existing behavior of *---* in TW's wikitext. - I reside comfortably in *maybe* territory here, weighing the potential confusion and surprise of future users against the expectations and existing use cases of current users. (My gut feeling is that the discrepancy *will* cause confusion for future users, while I'm uncertain how vested current users are in the current syntax.) It's possible we disagree on point #1, but I suspect the bulk of my disagreement with others rests on the thornier point #2. -- 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/f4b6ca31-bd7b-4b5b-9a52-d4e6d70b79cc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
