The ensoapi object now also provides a get_enso_learned_commands_folder so the learned-commands folder is available to commands.
Neither of these interfaces are currently used, but we need to build a "learn as open" command which is cross-platform, and that will use "learned_commands_folder".
Please confirm that this works on other platforms; I can confirm it works on Linux. Note that I may have *moved* the folder to somewhere more appropriate, which could mean that all your existing commands may need to be moved. Install the Enso Developers command from http://www.kryogenix.org/code/enso/ to easily find out where your installed commands are.
Provide extra interfaces for platform specific stuff.
If you want the folder where commands are stored, call:
from enso.providers import getInterface "scripts_ folder" )
getInterface(
and there are now two new interfaces:
getInterface( "learned_ commands_ folder" ) "data_folder" )
getInterface(
The ensoapi object now also provides a get_enso_ learned_ commands_ folder so the learned-commands folder is available to commands.
Neither of these interfaces are currently used, but we need to build a "learn as open" command which is cross-platform, and that will use "learned_ commands_ folder" .
Please confirm that this works on other platforms; I can confirm it works on Linux. Note that I may have *moved* the folder to somewhere more appropriate, which could mean that all your existing commands may need to be moved. Install the Enso Developers command from http:// www.kryogenix. org/code/ enso/ to easily find out where your installed commands are.