springer
I think he's doing very Good. "\n\n+" is a primary marker in actual written
WikiText. It is a fundamental *separation unit.*
Seems a very Good DEFAULT to split on after blanks.
*BUT *I'm sure Mark S. is aware you could split differently. SINCE blocks
like this ARE an issue...
<<<
My Hamster went feral.
--Pet fallacy
<<<
*A line START, After "\n\n" is *"<<<". It is likely easy to find
(simplifying slightly) regex = "\n{2,}<<<\n".
The ISSUE I think is any idea you need read blocks to do basic splitting.
I don't think you do in WikiText. *Merely regex for start of block*.
I think the issue is whether you looking to "Protect" blocks within a
COMPLEX parser, OR could be happy with INCREMENTAL SPLITTING.
What do I mean? You use a series of <<noto tag>> to reduce your WikiText to
smaller fragments in order matched to use case. Rather than a blunderbuss
complex code.
The point being only that START string should be enough most of the time in
actual WikiText usage.
Ask if this is not clear.
I footnote this with being explicit I don't actually know Mark's intent.
Best wishes
TT
On Sunday, 31 May 2020 03:07:22 UTC+2, springer wrote:
>
> Why not simply have noto refuse to split any paragraphs that would break
> any unresolved markup syntax? So
>
> <<<
> Three things I have trouble remembering...
>
> 1. When...
>
> 2. Why...
>
> 3. What was the question?
>
> <<< —Somebody
>
>
> would not get split up, nor would
>
> @@float:right; If I don't try...
> <hr>
>
>
> I won't succeed.
> @@
>
> That would suffice for most of my use-cases; if things belong together as
> an assertion-like unit, I'm often "wrapping" them in some way or other...
> Also, it seems that whenever we *do* use markup syntax, we will get weird
> effects if the opening and closing markup end up in different tiddlers. So
> this would be a good default behavior.
>
> -Springer
>
>
> On Saturday, May 30, 2020 at 5:13:40 AM UTC-4, bimlas wrote:
>>
>> As a matter of fact, the problem with this solution is that the essence
>> of the plugin would be lost. Then we need to approach the problem from the
>> other side:
>>
>> For example, putting a space in an empty line would not cut the paragraph
>> into pieces. However, this space must be deleted before saving the tiddler
>> in order for the text to actually appear as two paragraphs. But if you
>> delete it, the next time you edit it, there would actually be two
>> paragraphs, so the plugin would want to split it.
>>
>> That's not a good solution either ... I still have to think about
>> something useful.
>>
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/09ba9470-928e-4ded-b40c-18c746ce583a%40googlegroups.com.
