Hi, in an earlier forum post, Richard wrote
CodeRunner's 'run-in-sandbox' AJAX service, which is what the Ace-inline-filter is using, simply sends a complete job to the Jobe server which runs it and returns the results. There's no interactivity possible here. You can supply a text string to be used in lieu of keyboard input but Jobe just writes this to a file and runs the job with stdin redirected to that file. Input is not echoed to standard output so if there are, say, two successive reads from stdin with prompt strings Prompt A and Prompt B, the student will just see the output Prompt A Prompt B all on one line with no apparent input taking place. Unless they're carefully trained on what to expect, they will find this very confusing.
Is there anyway to avoid this behaviour, i.e. to automatically echo the stdin to stdout, so that it is less confusing to students? It would be good if the "expected" and "actual" strings could match exactly what the students see if they run this C program in their own console (i.e. outside of coderunner), where the stdin comes from their keyboard and is echoed to the console. Could we have a new question type e.g. "c-program-echo-stdinout" to do this? Or is there an existing solution? Thank you.