Currently, our configuration is split across two files, commands.conf and options.json. These should really just be one file with all the options and commands. This issue is probably best tackled by making a new “commands” object in options.json which contains a mapping from all the spoken commands to their shell commands.
Currently, our configuration is split across two files, `commands.conf` and `options.json`. These should really just be one file with all the options and commands. This issue is probably best tackled by making a new "commands" object in `options.json` which contains a mapping from all the spoken commands to their shell commands.
clara
Currently, our configuration is split across two files,
commands.confandoptions.json. These should really just be one file with all the options and commands. This issue is probably best tackled by making a new “commands” object inoptions.jsonwhich contains a mapping from all the spoken commands to their shell commands.Implemented and documented as of 8d4e46d5b3.