Matlab editor doubt - edit running code
6 views (last 30 days)
Hi all, I have a very silly issue with Matlab. I often run codes which go on for a couple of hours. I like to edit other codes during that time. So when I want to edit a code that is in the current directory, but not in the set of files currently open in the editor,it doesn't open immediately. It only opens after the currently running program is finished.(I am really dependent on the matlab error and warning pointers, so I don't like editing on other editors)
Does the latest version of matlab solve this difficulty?(I use Matlab R2010a). If not, how do I put this in a wish list for the developers to see?
RoJo on 10 May 2011
If you have access to a MATLAB Builder you can compile the long-running code and run them outside of MATLAB. There is no danger then with changing m files as they run (which is possibly why it is blocked via the workspace). Even on a computer with no MATLAB they run. http://www.mathworks.com/products/matlabxl/ It assumes though that you have a license.
Denis Zhegalin on 10 May 2011
You may open another instance of MATLAB for editing. But you will loose some RAM in this case.
Sean de Wolski on 10 May 2011
I just keep all relevant m-files open in the editor all of the time...
For when you don't have one you need open:
- open new m-file while running, copy in old function (after opening it in text editor), save it as that name, EDIT AWAY!
Oliver Woodford on 29 Feb 2020
In more recent versions of MATLAB, if you drag a file from a folder into the editor window, that file will open immediately, even when code is running. I'm not sure since what release this has been the case, but I've known about it for a while.
It's a real shame that right clicking on a function name in the editor, and selecting "Open ..." doesn't work immediately when code is running also, but waits until the code has finished. It's much more of a pain to have to find the file in a file browser window. This seems like an easy thing to fix.
Jared MacDonald on 3 Mar 2020
We have heard this pain from others and will fix this in an upcoming release. The short reason is that the action of opening a file flows through MATLAB (through the "open" and "edit" commands) regardless of how you do it, and so, when MATLAB is busy, those operations wait.
In the meantime, the workaround mentioned by Oliver (drag and drop) works to open a file when MATLAB is busy.