For readabilities sake, I made one final addition that allows to 'eat
away' any single blanks which immediately...
* precede the starting §§§
* follow the ending §§§
lookaheadRegExp: /\s?§§§((?:.|\n)*?)§§§\s?/mg,
Cheers, Tobias.
--
You received this message because you are subscribed to the Go
@tobias
==OT==
hihi, I did tell you :)))
==
>lookaheadRegExp: /((?:.|\n)*?)<\/showdown>/mg,
I think it should be or . showdown is the library.
right?
It's a nice plugin, but I think it should be either §§§ or .
Having two possibilities will be confusing and could cause a lot of
work in the f
Hi Paul,
Perfect, thanks a lot! Updated ShowDown [1] which should now be a
perfect little MarkDown variant for TiddlyWiki.
Cheers, Tobias.
[1] http://tobibeer.tiddlyspace.com/#ShowDown
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post
> However, if I try your code with any of the multiline ones, the
> linebreaks seem to break it [1].
lookaheadRegExp: /((?:.|\n)*?)<\/showdown>/mg,
> As for using §§§, I figured it looked nice in the sense of MarkDown's
> "it should look like what it means aproach"
Well given it's Tiddly
Hi Paul,
Thanks for the tip. One little asterisk ;o)
However, if I try your code with any of the multiline ones, the
linebreaks seem to break it [1].
Added you as a member to MarkDownTutor [2]. Have a look at the two
private tiddlers FailTest and ShowDown, the former being a test
tiddler, the la
> 1) I love having images in a slider format, I've been manually putting
> links of images into a tiddler, then using sliders pointing to those
> tiddlers, but I'd love if that function would be in either the slider
> function or img function.
Sounds like perhaps you want Eric's NestedSlidersPlugi
Hi there.
I've been wanting to comment on 2 things for a while which I'd feel
would be a (small) improvement.
1) I love having images in a slider format, I've been manually putting
links of images into a tiddler, then using sliders pointing to those
tiddlers, but I'd love if that function would b
Hi all,
txt2tags plugin is working nicely. I handled the "destructive" nature
of eating the formatter's "match:" element by making a modified
function using enclosedTextHelper as a base. You basically define a
"restore:" element as a text string of what match should have found...
it works in case
Hi Paul,
Thanks for the tip. One little asterisk ;o)
However, if I try your code with any of the multiline ones, the
linebreaks seem to break it [1].
Added you as a member to MarkDownTutor [2] ...have a look at the two
private tiddlers FailTest and ShowDown, the former being a test
tiddler and w
> There was some descussion about the default private/public value for
> new tiddlers.
That story is still pending - details here:
http://tiddlyspace.tiddlyspace.com/#%5B%5BSave%20Tiddlers%20as%20Public%20by%20Default%5D%5D
-- F.
--
You received this message because you are subscribed to the G
> xxx§§§
> This works already
> §§§yyy
>
> xxx§§§this doesn't§§§yyy
>
>[snip] how to change...
>
> lookaheadRegExp: /§§§\s*((?:[^\n]*\n)+?)§§§/mg
>
> ...to the desired one described above.
name: "showdown",
match: "",
lookaheadRegExp: /\s*(.*)\s*<\/showdown>/img,
worked fo
11 matches
Mail list logo
