As I was playing with DnD I noticed something strange about @edit. It supports section references @others. This could be dangerous when the @edit node contains a file originally written with @thin. Drag and drop could make this scenario much more likely.
I don't recall why @edit works this way. It doesn't make sense to me. Does anyone recall asking for the present @edit logic? By definition, when *reading* an @edit node, Leo reads the entire text (verbatim) into the single @edit node. Imo, @edit should work exactly like @nosent as far as writing goes. This should cause no harm: if you want fancier features, just convert @edit to @thin. Your comments please. (Quiet time does not apply to this topic.) Edward -- 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.
