The Twins are Unhappy!

[m i c h a e l]

It seems our friends [text] and [/text] aren't feeling well (v.8.8.9 on OSX UTF-8.) Try this in the shell (or not, you must ctrl-c then x to stop it from thinking about whatever it's thinking about so hard):

Code: Select all

> [text]
a
b
c
[/text]
^C
user reset -
(c)ontinue, (d)ebug, e(x)it, (r)eset:x
bash> _

Watch your processor(s) go nuts till you calm it/them down with the ctrl-c, x caress.

Is [/text] having an argument with [text]? Please talk to them, Lutz, and show them their differences are only syntax-deep ;-)

m i c h a e l

[cormullion]

On my system, the CPU skyrockets as soon as i press return after

[text]

It gives me a nice warm glow... (as the laptop starts to warm through... :-)

[m i c h a e l]

On my system, the CPU skyrockets as soon as i press return after [text]

Yep. Same thing happening here. This G5 hovers at around 1-3% most of the time, so I guess it can handle it ;-)

m i c h a e l

P.S. I'm working on the next (newlisper) post. Hope to be done by tonight!

[Lutz]

This is fixed in 8.8.10

Code: Select all

newLISP v.8.8.10 on OSX, execute 'newlisp -h' for more info.

> [text]

missing end of text [/text]
> 

Lutz

[Lutz]

... and of course one should never do it. When entering multiline [text] ...[/text] strings interactively enclose in [cmd], [/cmd] tags each on a sperate line:

Code: Select all

newLISP v.8.8.0 on OSX, execute 'newlisp -h' for more info.

> [cmd]
[text]
asf
asf
[/text]
[/cmd]
"\nasf\nasf\n"
> 

and then is works also on older versions.

Lutz