Dear all,
the reported problem does not seem to concern matlab-shell at all. So my
email can be ignored here.
I found out the similar problem happens in 2018b but for legend command
when run in matlab-shell, and then I found out that this problem is also in
2018a if run from terminal. It does not depend on matlab-shell in emacs. It
seems to depend on the order i ran different versions of Matlab.
It rather seems that the problem might be connected with three Matlab
installations, so i will investigate. Maybe my ~/pathdef.m is not loading
all the paths because it gets overwritten by another matlab? Anyway, i
apologize for disturbing a wrong list.
0.
On Tue, Jan 29, 2019 at 7:00 PM Ondra Kamenik <ondra.kame...@gmail.com>
wrote:
> Dear all,
>
> matlab-mode.el is great! I have been using it for years with great
> satisfaction. Thank you for your work.
>
> I installed today 2018a and also 2018b. My previous version was 2015b. If
> I run matlab in Emacs matlab-shell-mode than I get the following error when
> calling "system('ls')" for example:
>
> >> format compact
> >> system('ls')
> Undefined variable "matlab" or class
> "matlab.io.internal.utility.convertStringsToChars".
> Error in dos (line 65)
> [varargin{1:nargin}] =
> matlab.io.internal.utility.convertStringsToChars(varargin{:});
> >> usejava('jvm')
> ans =
> logical
> 1
> >> ver('MATLAB')
>
> -----------------------------------------------------------------------------------------------------
> MATLAB Version: 9.4.0.813654 (R2018a)
> MATLAB License Number: 40706422
> Operating System: Linux 4.19.13-300.fc29.x86_64 #1 SMP Sat Dec 29 22:54:28
> UTC 2018 x86_64
> Java Version: Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM)
> 64-Bit Server VM mixed mode
>
> -----------------------------------------------------------------------------------------------------
> MATLAB Version 9.4
> (R2018a)
>
> If I run the same in matlab-shell for R2018b, i don't have any problem. If
> i run matlab 2018a from terminal with "-nodesktop", i don't have any
> problem either. The only problem is a combination of 2018a and
> matlab-shell. I checked outputs of matlab -n and matlab -e run from
> terminal and from matlab-shell, but i did not find any difference which
> could cause it.
>
> Many thanks for any leaders. Unfortunately, i cannot replace 2018a with
> 2018b as we have a lot of codes which still need be ported to 2018b.
>
> 0.
>
_______________________________________________
Matlab-emacs-discuss mailing list
Matlab-emacs-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
