Matlab Editor does not respond to keyboard inputs

Hi Everyone,

My Matlab editor stopped responding to most (but not all!) keyboard inputs. All letters+numbers stopped working, and SPACE as well, but BACKSPACE still works. And Ctrl+C/V also works, but not C or V??? Matlab editor is the only one with this problem, my command window does not have any problems. I'm flabbergasted!

Laurens

ps. Version is R2013a, running on Windows 7 Professional, 64-bit.

ps #2. The problem disappears on restarting Matlab. I'm still very curious though, so if anyone has any ideas...

[Oleg Komarov]

How many lines are your scripts?

[Jenny]

Same problem on 2012b. Very annoying.

[Jenny]

Less than 100

[iisakson]

I have the very same problem on 2015b for a function file.

[Johannes]

Same Problem for me, running 2017a. Had it happen twice on different files already.

[Beatrice Lena]

Problem still there with 2018a...

[Jan]

Nobody has posted the currently edited M-file here. The user d p posted at least a screenshot: A script starting with clear all and the editor is in the state "continue enter a statement".

I still think, that there is a common pattern behind the different observations. Therefore I encourage all users to add the corresponding code in this thread.

Please give us a chance to idnetify the problem.

[hamed amini]

the same problem with

MATLAB Version: 9.9.0.1467703 (R2020b)

Operating System: Microsoft Windows 10 Enterprise Version 10.0 (Build 19044)

Java Version: Java 1.8.0_202-b08 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode

[Alf Magne Meling]

Same problem with keyboard input stop working in edit window.

The edit window was dragged out of the main Matlab window onto a separete display when this happened.

Close the window and open and move again, and everything work ok.

Version

R2019a (9.6.0.1072779)

64-bit (win64)

March 8, 2019

Answer 1

[Zzz]

A solution that worked for me:

Right click the live editor path -> click Restore

[Lucy Wiseman]

This worked for me - Thank you!!!

[Twinkle Bagha]

it worked for me as well....Thank you so much !!!!!

[Najia]

worked thank you!!

[kh]

but where is the live editor path, plzz?

Answer 2

[OIS]

I have the same issue with R2016a on win7 64-bit machine (only non-escaped keyboard strokes are not accepted). However, I noticed that it only is a problem to the one file I am working with and all other files open in the editor don't have this issue. I used to close Matlab and reopen it and it would solve the problem. Now, I closed the one file with the problem and reopen it and it was fine. A work around but not a solution. Help is definitely still needed!

Answer 3

[Eviatar Yemini]

I think I solved it. Noticed a suspiciously timed Java update that coincided with the issue.

The problem was slowing both my Matlab editor & compiled standalones, so that added to the suspicion that it's a Java issue.

Downloaded the latest Java SE & SDK, then installed them. Problem dissapeared.

[Joshua Diamond]

Nicely done. It looks like this fixed it for me.

Answer 4

[Matthew]

No idea how to fix it, but I have this problem too. Also 2013a, also Windows7 Pro 64 bit.

My problem corrects when restarting matlab, but my scripts take several minutes to load + process, so it's a bit annoying.

Answer 5

[d p]

Same here, with an attached pic. r2016, restarting solved my problem.

Answer 6

[Mina Gheiratmand]

Same issue here. Using Matlab 2018b on Mac. It has happened multiple times working on different codes. Code is not too long. (I feel this time, it might have started when I pressed multiple keyboard buttons at the same time while typing. I checked the keyboard shortcut list in Preferences but no keyword search led to a useful hint there.)

A maybe useful observation is that when I undock the editor or the command window, the keyboard strokes are recognized again and I can type. But when I dock them back into the main Matlab window, the typing is not recognized again.

p.s. I do not see a "continue entering statement" comment.

Answer 7

[yapeng shi]

Please check Matlab keybord shortcuts perferences. Maybe it's because you use 'C', 'V' or other characters as the shortcuts to response the action rather than typing.

Answer 8

[Johann Martinez]

Matlab R 2020b also freezes on keyboard after some runs!!!

Are here some workaround about this issue?

Thanks in advance.

[Joshua Diamond]

I found a strange workaround. This is creating any error (like try typing saveas with no arguments). Of course this would have to be done before the error occurs. Then once you have the inability to type, you can click the red error text. This pops up a little information window. After this, you should be able to type.

Answer 9

[Joshua Diamond]

I found a strange workaround. Some things have worked including right clicking the command window and clearing it; running a function (by clicking the name of the function in recent commands); opening a new editor window and closing it.

But one thing works most reliably. This is creating any error (like try typing saveas with no arguments). Of course this would have to be done before the error occurs. Then once you have the inability to type, you can click the red error text. This pops up a little information window. After this, you should be able to type.

I'm using 2020b, Mojave 10.14.6. I'm also screen sharing.

Answer 10

[Haris K.]

Same problem here. I am using MATLAB R 2020b.

Same issue like everybody else. Shortcuts like Ctrl+C and Ctrl+V work. Selecting part of code and hitting F5 works. Arrows (up,down,left,right) work. Backspace works. Anything else, does not work.

I have (and had prior to execution) other script files open, and everything works as expected (to those other scripts). Nothing really suspicious appears, neither any message in the status bar at the bottom (i.e. next to the parallel pool icon).

I had been running this code for a few days, I tried making some changes to the code while running. Usually this works, but it wouldn't allow me any changes (i.e. keystrokes stopped functioning) after some time. At first, because the script was still running, I thought that this is something MATLAB is doing to avert some issue due to the fact that the code was still running. Then the code stopped (-I forced it to stop because I needed the results to catch a deadline), but the issue continued and I sought a solution in the forums. Unfortunately, no solution yet.

[Haris K.]

Let me add that colsing and re-opening that paritcular script (-just the script is enough; not the entire MATLAB session as someone else suggested), corrected my issue.