Upon typing anything into the command window, the answer is only outputted into the workspace, and not into the command window as the typically expected "ans = ___" line:

Even typing gibberish generates no output or any error handling. It just prompts the next line:

Running a program with internal error handling will work, but it seems things such as type errors or other MATLAB-handled errors are ignored, and there are no ways to generate outputs, unless I force it with disp(). But I obviously don’t want to keep doing that nor is that a viable solution going forward.
A coworker was trying to help me with this and we discovered that running "evalc" in the command window generates the same problem on his MATLAB as my current issue. I don’t remember ever running "evalc" unless I ran a script at some point that had that included. There seems to be no known solution out there for how to reverse the effect of this "evalc" and/or turn it off.Upon typing anything into the command window, the answer is only outputted into the workspace, and not into the command window as the typically expected "ans = ___" line:

Even typing gibberish generates no output or any error handling. It just prompts the next line:

Running a program with internal error handling will work, but it seems things such as type errors or other MATLAB-handled errors are ignored, and there are no ways to generate outputs, unless I force it with disp(). But I obviously don’t want to keep doing that nor is that a viable solution going forward.
A coworker was trying to help me with this and we discovered that running "evalc" in the command window generates the same problem on his MATLAB as my current issue. I don’t remember ever running "evalc" unless I ran a script at some point that had that included. There seems to be no known solution out there for how to reverse the effect of this "evalc" and/or turn it off. Upon typing anything into the command window, the answer is only outputted into the workspace, and not into the command window as the typically expected "ans = ___" line:

Even typing gibberish generates no output or any error handling. It just prompts the next line:

Running a program with internal error handling will work, but it seems things such as type errors or other MATLAB-handled errors are ignored, and there are no ways to generate outputs, unless I force it with disp(). But I obviously don’t want to keep doing that nor is that a viable solution going forward.
A coworker was trying to help me with this and we discovered that running "evalc" in the command window generates the same problem on his MATLAB as my current issue. I don’t remember ever running "evalc" unless I ran a script at some point that had that included. There seems to be no known solution out there for how to reverse the effect of this "evalc" and/or turn it off. command window, output, evalc MATLAB Answers — New Questions

​