Dump uninterpreted text to editor window at cursor location

[Michael-Overall]

The mic-testing branch (check commit history to see if it is merged with master yet), contains some starter logic to take mic input, put it in a file, then parse the file's contents to text, and spit it out via console.log.

It may be possible to grab the contents of the 'stdout' variable returned by this process, and dump it to the editor screen. See this article to get a start on research. This cuts out the ultimate goal of parsing certain words to specific characters (ie 'p tag' prints

) but a good 'ol text dump would take us one step closer to putting valid commands/text into the editor's code window.

We can probably grab the text that was being spit back to the command line and try to pass it into the editor's window (see this article on putting text in the IDE

in extension.js:

    startMic.then(function () {
        spawn.exec('python ' + pyScriptLoc, {cwd: __dirname}, (error, stdout, stderr) => {
            console.log("going to gather the words...")
            if (error) {
                console.error(`exec error: ${error}`);
                return;
            }

//we may be able to grab the text in the 'stdout' variable and shove that into the editor console.log(Words you spoke: ${stdout}); }); })

});

[Michael-Overall]

this issue is still doable if you pull the mic-testing branch, and fix the directory routing. You will have to use __dirname in some of the script files to construct paths relative to the running script instead of hard coding an absolute path. This was done in the code in the Dockerization pull request, which hasn't been approved/merged yet (partially because that code only works with unix hosts).

You will also need to fix the directory routing in the python script file. Again, you can refer to the pull request mentioned above.