World: r3wp

you know p: and :p in parse-rules?

k I will try it thank u :)

yargh. I know how to split with a single character as the delimiter:

	chunks: parse/all text "^/"


How do I split where a blank line (2 newlines with nothing in between) 
is the delimiter? The naive solution I can think of just doesn't 
work:

	chunks: parse/all text "^/^/"

you can make up a rule.

lines: copy []
rule: [ copy txt to "^/^/" (append lines txt) skip 2 ]
parse mytext [ some rule ]

untested ...

I get lost trying to find a good way to describe my rule. Here's 
the bad code that states my intent, but doesn't work ('parse doesn't 
seem to like having that 'until in there)

chunks: parse/all text [
	until [
		chunk: copy ""
		copy chunk to "^/^/"
		skip
		if chunk [
			append chunks chunk
		]
	] 
]

ummm.. don't think you can do that

nope, I discovered that :-D

parse expects to see a parse dialect if you following it with a block

try my way ...

and your code is mixing rebol code with the parse dialect.

Rebol code has to be in ( ) when used within the dialect

oh okay. I understand that now.

that should be

parse/all mytext [ some rule ]

thanks

np

Hm. Still having issues:

>> rule: [ copy chunk to "^/^/" (append lines chunk) skip 2 ]
== [copy chunk to "^/^/" (append lines chunk) skip 2]
>> text: "Dude.^/^/Sweet!^/"
== "Dude.^/^/Sweet!^/"
>> lines: copy []
== []
>> parse/all text rule
** Script Error: Invalid argument:
** Near: parse/all text rule
>>

oh, wait.

oops .. should be "2 skip" and not "skip 2"

That's okay, I forgot to include the possibility that there would 
be only one line, so my tests were blowing up somewhere else.

Hm, that misses the last line if the text doesn't end in "^/^/"

easy enough .. add {^/^} to end of text before parsing

That *is* a nice and easy solution, thanks a lot!

sweet, all my tests pass now. Time to add more tests :-)

sometimes I find it easier to change the data than to change the 
rule :)

Hey, as long as it works.

Working on a textile parser over here to build my 'parse skills and 
make it easier to build my website with Rebol

not that you shouldn't do it, but I use http://www.rebol.it/~steel/retools/remark/

I'm <>-phobic ;-)

Remark takes care of all of those taggy things

and all of my pages are already in textile format, and I think a 
few of my friends would be more interested in Rebol if I had a textile 
parser for them

what's textile ?  A type of fabric ?

http://hobix.com/textile/

A structured text variant ...

yep

I like some of the different structured text formatting systems

Volker thank you it works great now and the code rule is tiny ;)

:)

Any parse suggestions for trying to find #"(" without a matching 
#")" in text that might also have proper pairs of parens?

you probably need to count them and see where you end up after finding 
all parens. I'm not sure if it can be used to see which are missing...

That would probably work fine. This if for the textile parser, where 
a declaration like "p(." means a paragraph with left margin of 1em, 
repeated for additional ems of margin. Counting will be quite useful.

count one up on #"(" and one down on #")". If correct, the end result 
is zero.

thanks

Perfect, Henrik. That took me exactly where I needed to go for this 
feature.

Gonna have to work on my test-simple.r script soon to provide better 
summaries. The number of tests that are passing in this thing is 
getting rather large!

Any tips on how to convert " *text* " to " <strong>text</strong>"?

One way:
   replace text "*" <strong>
   replace text "*" </strong>

If there are multiple pairs of "*", repeat in a loop until the length 
no longer changes

You should look at make-doc text to see how it parses stuff.  I believe 
it's a similar problem.

source not text.

Brian, you can look at my NicomDoc format http://home.tiscali.dk/john.niclasen/nicomdoc/

Look for the 'magic' in "nicomdoc.r", where you'll find rules for 
such things. (I guess, you have to handle multiple ****.