John Ciolfi <john.cio...@mathworks.com> writes:
> 2. Enabled debugging of matlab code (dbstop, etc.) in R2015b MATLAB and > later. This requires using the MATLAB editor instead of emacs because > recent > MATLAB's are not giving enough info to debug within emacs. I'm confused: I thought this was fixed already? I am using R2016b with the latest version of matlab-mode from MELPA and debugging works great using GUD. I believe someone wrote a patch that prints the correct hotlinks. Could we have some clarification on this? > - matlab.el: fixed TAB completion handling. Prior to fix, hitting tab would > generate noise (new unnecessary ">>" prompts) and it didn't handle certain > cases, e.g. ">> ! mv file.<TAB>", ">> set(h,'<TAB>')", etc. would fail to > complete. This is a great fix! ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Matlab-emacs-discuss mailing list Matlab-emacs-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
