Matlab stops taking inputs...
Show older comments
Sometimes when I run a bad .m file Matlab will sort of become unresponsive... it's not a total lock up, because I can still type whatever I'd like in the workspace but after hitting return it just bumps me down a line and doesn't actually execute the command. Why is this and how do I avoid it / stop it?
1 Comment
Matt J
on 2 Jan 2013
What do you mean by a bad .m file? What's bad about it?
Answers (1)
Sounds like MATLAB simply hasn't finished executing the previous commands. Be patient, or investigate why your previous commands are doing a bigger computation than you intended.
1 Comment
Sean de Wolski
on 2 Jan 2013
Sounds right to me. Does it say busy in the bottom left corner?
Categories
Find more on Entering Commands in Help Center and File Exchange
on 2 Jan 2013
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!
