On 12. Jan, 01:37 h., HansBKK <[email protected]> wrote: > On Thursday, January 12, 2012 6:30:35 AM UTC+7, Terry wrote: > > > On Wed, 11 Jan 2012 14:35:57 -0800 (PST) > > Juraj <[email protected]> wrote: > > > > Support of other languages or @shadow nodes (to cooperate with people > > > that don't use leo) feels more like experiment. > > > It may be that shadow nodes need more testing, particularly with > > languages other than Python. I've used them without any particular > > issues, but then I decided I preferred @auto.
Leo does not support JSP automatically, it has only basic syntax highlighter for it, and I doubt it ever will be able to do it correctly, as JSP is very complicated format itself, moreover it is layered on top of HTML. What I do is to put the file into outline manually, and expect Leo to maintain the structure for me when file changes. It does this quite well (when it works, of course). > I'm curious as to how the choice of language would impact @shadow > functionality. At least for 2 reasons: 1. Leo is sensitive to indentation 2. needs to use right comments with sentinels, so that something else in the file won't confuse it. I believe I had problem with this as well, but could not easily reproduce it so far. > I've been using them with plain text-as-text files and haven't come across > issues, but also haven't done any systematic testing. I also have the extra > "security blanket" that I make sure any files I'm manipulating with Leo are > under version control, as I'm very aware that my limited understanding of > Leo is a lot more likely to lead to data loss than any bugs. If the data loss is accompanied by unresponsive interface, missing menus, exceptions and inopenable Leo files... then I doubt it is caused just by my "limited understanding"... > Juraj, when the time comes and you want to do some "stress-testing" with > cloning, have a look at a "standard operating procedure" I've proposed to > be documented > here<https://groups.google.com/d/msg/leo-editor/j7BOnRqCFcI/1jIavoqXxLUJ>. Thanks, I'll bookmark that.. > Further up in that thread I also point to a different SOP the developer > pointed out in the past to try also. I'd appreciate any feedback you might > have on these as a method to avoid problems with safely keeping nodes in > multiple @files, in case that's one of your needs as well, as that's > generally considered dangerous. To this moment I was not aware at all there is such thing as "standard operating procedure"... and even if it would be right in leo's official docs, good luck to have all new users read and follow it :-) > I would also suggest regarding the problem's you've perceived with @shadow, > create a new .leo file with a minimal test case to demonstrate any problems > and I'm sure prompt attention will be paid to them if you post them here. Yes I did several times already, but some problems I encountered are hard to reproduce and they need hours, if not days to come up with minimal test case. Juraj -- 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.
