On Mon, Aug 25, 2014 at 2:20 AM, Fidel N <[email protected]> wrote:
> So I thought there might be a way for non-programming experts to add to Leo > with useful snippets. ... > I would really like for useful scripts not to fade away instead of > persisting inside Leo What you want is reasonable. > so I thought we could add a commands branch inside leoSettings.leo with > useful snippets. Hmm. leoSettings.leo is not a great place for user contributions. Imo, we should keep changes to leoSettings.leo to a minimum. At present, there are two choices, neither satisfactory: 1. Put the code in leo/scripts/scripts.leo 2. Put the code in the contrib branch. The problem with each is that the code does not become active, as you want. The obvious solution would be to load code in some other .leo file, say leo/config/contrib.leo I was about to say that this looks insanely dangerous in the present collaborative environment, but in fact we all are *always* assuming that anyone with commit access to the git repo is completely trustworthy. In other words, if we do allow leo/config/contrib.leo to be loaded automatically, we have got to be *sure* that contrib.leo is safe at all times. I am uneasy about this... Your comments please, amigos. Edward -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
