Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2020-01-05 Thread Eric Ludlam
Hi Shervin & Roman, John Ciolfi also encountered this MAC issue, and had sent me a patch. I don't have a MAC, but I verified his patch still worked for me on Windows w/ the netshell extension, and on Linux. I pushed his change to a "mac_init" branch for testing. To use it, you can pull the ma

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2020-01-05 Thread Shervin Safavi
Thanks Roman, Uwe, and Eric! I tried Roman's solution and it actually works and resolves the error I explained earlier. But I guess there are still some issues: When I execute “edit ” I will receive this error: Error using edit (line 66) Could not find external editor '' Although this line: "ema

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2020-01-04 Thread Uwe Brauer
>>> "RG" == Roman Garnett writes: > Hi Eric, > I had the same issue as Shervin using matlab-mode installed via MELPA > with emacs 26.3 on OS X 10.15.1. The MELPA version number for > matlab-mode is 20191223.2012. The issue was that the toolbox/+emacs > directory was for some reason

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2020-01-04 Thread Uwe Brauer
>>> "RG" == Roman Garnett writes: > Hi Eric, > I had the same issue as Shervin using matlab-mode installed via MELPA > with emacs 26.3 on OS X 10.15.1. The MELPA version number for > matlab-mode is 20191223.2012. The issue was that the toolbox/+emacs > directory was for some reason

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2020-01-04 Thread Roman Garnett
Hi Eric, I had the same issue as Shervin using matlab-mode installed via MELPA with emacs 26.3 on OS X 10.15.1. The MELPA version number for matlab-mode is 20191223.2012. The issue was that the toolbox/+emacs directory was for some reason not installed by emacs; after checking out the repo and man

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2019-12-31 Thread Eric Ludlam
Hi Shervin, It looks like you have two different versions of matlab-emacs on your two machines.  I changed how things are setup to be clearer.  emacsinit now deals with the path, and debugging stuff.  The 'emacs' package in matlab includes a set command (thus : emacs.set) for configuring tools

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2019-12-28 Thread Shervin Safavi
Hi Uwe, I follow your advice. emacsinit is running smoothly and it prints: Updating MATLAB Path to support Emacs toolbox: addpath(... But it give an error when running the following: emacs.set('clientcmd', 'emacsclient -n -s /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s8gn/T/emacs501/server-948

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2019-12-28 Thread Uwe Brauer
>>> "SS" == Shervin Safavi >>> writes: Hello Shervin, > Dear everyone, > I'm setting up matlab-mode on a laptop with mac OS. When I run matlab-shell > I get the following error: > "Unable to resolve the name emacs.set." > when it's running: "emacs.set('clientcmd', 'emacsclient

Re: [Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2019-12-26 Thread Uwe Brauer
>>> "SS" == Shervin Safavi writes: Hi, > Dear everyone, > I'm setting up matlab-mode on a laptop with mac OS. When I run matlab-shell > I get the following error: > "Unable to resolve the name emacs.set." > when it's running: "emacs.set('clientcmd', 'emacsclient -n -s > /var/folders/r5/zx0tj5s

[Matlab-emacs-discuss] issue with setting up matlab-mode on mac OS with MATLAB 2019b

2019-12-26 Thread Shervin Safavi
Dear everyone, I'm setting up matlab-mode on a laptop with mac OS. When I run matlab-shell I get the following error: "Unable to resolve the name emacs.set." when it's running: "emacs.set('clientcmd', 'emacsclient -n -s /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s8gn/T/emacs501/server-28543');"