On Sat, 24 Feb 2018 11:31:10 -0600 "Edward K. Ream" <[email protected]> wrote:
> On Sat, Feb 24, 2018 at 8:25 AM, Terry Brown <[email protected]> > wrote: > > So Kent's hash idea is very good, but for now you can already do this, > > albeit needing to know the potential risk. > > > > I agree with what all you say. > > Imo, #740 Execute .leo/leo_startup.py on startup > <https://github.com/leo-editor/leo-editor/issues/740> is simpler and > safer. Sure, although the per outline specificity of @script nodes is useful. But unless we're going to remove @script nodes I don't think it's up to us to try any decide if a user can manage the risk safely or not, and whether they should know about the feature. Realistically most Leo users will never receive a .leo file from someone else, so while the potential risk of @script is very high, most of the time the actual risk is quite low. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
