Mark,

Yes perhaps this is true, but the current edit widgets, and the core editor 
all accept the <enter> and imbed line feed in text area fields. Somehow we 
need to get this to occur in demand, I wonder if a regex could extract it 
from a known tiddler an store it in a variable we can append later?

It would be a nice pre-provisioned variable.

I have actually being considering the use of ¶
¶ 182 &para; pilcrow sign
Perhaps this could be a way to get the editor to treat a sentence like a 
paragraph and wrap it in P tag on render.


Regards
Tony

On Monday, May 18, 2020 at 4:05:58 AM UTC+10, Mark S. wrote:
>
> I don't think it is possible with the current operators and widgets. I 
> think it would take a javascript macro to do the substitution.
>
> On Saturday, May 16, 2020 at 9:14:05 PM UTC-7, Tony K wrote:
>>
>> oh thank you Mark, I should have asked days ago
>>
>> a follow-up question please, is there a way to "add" '\n' that is not 
>> using <br /> 
>>
>> i.e in TWCrosslinks when then entry is added to the input box the plugins 
>> appends it to a tiddler, for now I am using <br /> which, visually, doesn't 
>> look so good if you open the tiddler.
>>
>> thank you 
>>
>> On Sunday, May 17, 2020 at 12:11:10 AM UTC+3, Mark S. wrote:
>>>
>>> You can use the splitregexp operator. Here's an example that works on 
>>> TiddlyWiki.com:
>>>
>>> <$list filter="[[HelloThere]get[text]splitregexp[\n]!is[blank]nth[3]]">
>>> <$text text=<<currentTiddler>>/><br/>
>>> </$list>
>>>
>>>
>>>
>>> On Saturday, May 16, 2020 at 1:38:03 PM UTC-7, Tony K wrote:
>>>>
>>>> I'm unable to find the delimiter equivalent to \n in TW5
>>>>
>>>> Assuming I have a tiddler and I want to parse it line by line. Is it 
>>>> doable? 
>>>>
>>>> Thanks 
>>>>
>>>>

-- 
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/644b6faf-f1bc-438f-bf77-f85f81ad8e3b%40googlegroups.com.

Reply via email to