On Dec 12, 5:50 pm, Terry Brown <[email protected]> wrote: > When you're more experienced with Leo you'll still be able to miss that > log message and spend a lot of time wondering what's going on :-} Probably won't happen if I can't fix my problem, which will be a "no go".
> This condition definitely needs more sirens and flashing lights. > > Just to clarify - did you're original before Leo touched it .js file > include "<< something >>"? I'm not sure about this question? my var text1 = "<< some text >>"; is just a text1 variable that contains the text "<< some text >>" that's it. > << sectioname >> has a special meaning in Leo, for which you might be > invoking unintentionally? hmm .. unintentionally .. kind of. Since someone else wrote the code, I just don't know, what comes up. But I did know, what <<..>> means in leo. I just couldn't connect the error messages, with the js code. The "problem" here is, the project I want to work with, uses << ...>> all over the places in js code, and even more in its documentation but not for leo sections. I did have a look at the leo source code and the "<<" ">>" parsers seem to do the same :)) All hardcoded, which makes the dilemma perfect. The @verbatim would work as an escape mechanism, for may be 10 lines, but not in every second line of documentation text. thx for your attention. -m -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
