On 1/15/2014 7:39 AM, Edward K. Ream wrote:
On Wed, Jan 15, 2014 at 6:03 AM, Matt Wilkie <[email protected]
<mailto:[email protected]>> wrote:
A required environment variable to enable processing startup
scripts seems like a reasonable precaution. And/or perhaps a
command line option?
leo --autoexec=True %home%\workbook.leo
​Good idea. But I think the more locks the better. The environment
variable *and* the command-line option. What do you think?
Edward
I vote *just* for the command-line option. Too many locks and the
feature becomes useless, at which point why not just remove it completely?
I think there are valid usecases for @script nodes. They are limited,
but valid. I don't think an environment variable is the way to go here
-- that makes it *extremely* difficult for a user who mostly lives in
Linux-land to get their .leo to work in Windows. (Familiarity and such
-- it would take a good deal of googling for them to figure out the
process.)
Additionally, such precautions don't prevent rogue plugins from enabling
scripting anyways... all it would take is a
`c.theScriptingController.atScriptNodes = True` followed by
`c.theScriptingController.createAllButtons()` on their create hook to
enable it and cause a bit of trouble...
In short, I don't think that there is *any* full solution to this
problem. But adding an env var *and* a command-line switch *and* a
config setting is a bit much. The only real risk I think is the setting
*outside* of myLeoSettings.leo.
-->Jake
--
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/groups/opt_out.
