Re: [Matlab-emacs-discuss] Missing execution line pointer after upgrading Matlab

[Eric L. <Eri...@ma...>]

Hi,

I have looked into this, and in Earlier MATLABs I used to take advantage of a “bug”, which I thought was a feature, that allowed MATLAB to send me html like anchors which I could interpret.  MATLAB is now correctly identifying that it is not pointing at a device that supports anchors (since it is a plain pty), so I don’t have the data.

I asked a couple folks about this and I don’t believe there is a trick I can pull to get this data to be output to Emacs with the newer MATLABs, which leaves things kind of broken.

Before the links, I used to interpret the plaintext, but this was buggy, and simple output tweaks from MATLAB, or locale changes would mess it up, so it doesn’t seem too good either, but could be resurrected.  I don’t really have the bandwidth for that kind of refactoring project though. ☹

Eric

From: Odd Andersen [mailto:odd...@gm...]
Sent: Wednesday, January 27, 2016 8:21 AM
To: mat...@li...
Subject: [Matlab-emacs-discuss] Missing execution line pointer after upgrading Matlab


Hi,
After I upgraded my Matlab version from R2014a to R2015b, I can no longer see the little arrow that indicates the current execution line while debugging matlab code using matlab-emacs.  Moreover, debugging seems to work poorly in other ways: it apparently no longer brings up the relevant code buffer while debugging (possibly tied to the problem above), and when arriving at a multi-line function call (i.e. where each line of text is continued with '...'), it no longer treats this as one line but insists on stepping over each text line separately.
I saw someone else (Tunc Aydin) mentioned the missing execution line pointer on this mailing list last fall, and was answered by Eric Ludlam that apparently the "output Emacs was interpreting for the debugger has changed" and that this .  (http://sourceforge.net/p/matlab-emacs/mailman/message/34601964/)
Has anyone looked into this since then?  matlab-emacs has worked wonders for me in the past, and it's very sad if it stops providing a practical debugging tool  as people upgrade to newer versions of Matlab.
Best,
Odd Andersen