On Tue, Oct 2, 2012 at 5:06 PM, F.S. <[email protected]> wrote: > I think we have a little misunderstanding of what emacs buttons are. They are > close cousins of text-properties. They make any text (a word, a character or > a region) clickable by associating function hooks to the text, akin to > hyperlinks. This is very useful for exploring data by making the data active.
This would make a good plugin, imo. Qt supports hyperlinking, and the plugin could associate hyperlinks with nodes using the so-called user data in p.v.u. > What I was referring to was that when we eval everything at the top level of > course we break all the module restrictions. I have no idea what you are worried about. Yes, using g, c and p scripts can access all data and all of Leo's source code, but the access is perfectly controlled and has never, to my knowledge, caused any problems whatever. > And intermingled with interactive sessions, it is easy to interactively set > something but then to forget to have it in the actual code. Yes, you could set ivars or redefine methods or functions from, say, pdb, but I've never been tempted to do that, nor do I see that it would be that useful to do that. This FAQ entry describes how I safely use Leo to develop itself: http://webpages.charter.net/edreamleo/FAQ.html#how-can-i-use-leo-to-develop-leo-itself The trick is that you test Leo (or any "unsafe" script) in a separate copy of Leo, which should load very quickly, and which you can invoke using only one or two keystrokes. HTH. 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.
