Change default behavior to recognize single line breaks

99 views
Skip to first unread message

chishaku

unread,
May 23, 2014, 2:05:32 PM5/23/14
to tiddl...@googlegroups.com
Hi all,

Is it possible to change the default behavior to recognize single line breaks?

I know that I can use the """ ... """ syntax for hard line breaks in wikitext but if possible, I'd like to reverse the behavior so that single line breaks are recognized by default and perhaps I could use the """ ... """ syntax to ignore single line breaks.

Thanks in advance for any suggestions.

Jeff

chishaku

unread,
May 23, 2014, 2:08:08 PM5/23/14
to tiddl...@googlegroups.com
Forgot to mention that I'm using TW5.

Jeremy Ruston

unread,
May 26, 2014, 2:58:45 PM5/26/14
to TiddlyWiki
Hi Chashaku

The current behaviour follows standard MarkDown. There is a ticket for adding support for GitHub Flavoured MarkDown, a variant dialect of MarkDown that supports single line breaks as hard line breaks:


My plan is to fix this as part of an upcoming round of changes to the parsing infrastructure, perhaps for 5.0.13 or 5.0.14.

Best wishes

Jeremy


--
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 tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.



--
Jeremy Ruston
mailto:jeremy...@gmail.com

Duarte Farrajota Ramos

unread,
Oct 23, 2016, 7:31:54 PM10/23/16
to TiddlyWiki, jeremy...@gmail.com
Is there any way to make the """.....""" work for transclusions?

I have several tiddlers in wish I would like to includesome fields content; I currently end up using bullet points as a quick way to make hard line breaks, but being able to do so automatically would save a whole lot of trouble.
I can't seem to make """{{!!Field_Name}}""" work unfortunately, it wont propagate the effect into the transclusion. Any workarounds or is it a limitations of the current system?
Reply all
Reply to author
Forward
0 new messages