matlab-emacs-discuss — Discuss Emacs/MATLAB integration

Re: [Matlab-emacs-discuss] Problem with make command

[Ollie H. <ol...@dr...>]

Thanks. No worries I figured it out already, I should’ve updated the
request.

All the best,

Ollie

On Sat, 13 Jun 2020 at 04.56, Eric Ludlam <eri...@gm...> wrote:

> Hi Ollie, I missed your email when you first sent it.  Sorry.
>
> It looks like you have a different flavor of Emacs installed.  To use
> the Makefile, you can do this instead:
>
> make EMACS=spacemacs
>
> or
>
> make EMACS=/path/to/my/emacs
>
> Hopefully that helps you get going!
>
> Eric
>
> On 5/28/20 3:55 PM, Ollie Hulme wrote:
> > Dear experts,
> >
> > I am having issue compiling matlab-emacs via the make command
> >
> > As instructed, I cd to the matlab-emacs folder, then make yields the
> > following error:
> >
> > /emacs -batch --no-site-file --eval '(setq debug-on-error t)' -L ./
> > --eval '(setq generated-autoload-file /
> > /"/Users/olliehulme/matlab-emacs/matlab-load.el")' -f
> > batch-update-autoloads /Users/olliehulme/matlab-emacs
> > make: emacs: No such file or directory
> > make: *** [autoloads] Error 1/
> >
> > Spacemacs v.0.200.13
> >
> > Any ideas how i can proceed?
> >
> > Ollie
> >
> > --
> >
> >
> >
> >
> > _______________________________________________
> > Matlab-emacs-discuss mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>
>
> --
Ollie Hulme
Senior Researcher
Reward & Homeostasis group
Danish Research Centre for Magnetic Resonance
Copenhagen University Hospital Hvidovre
(+45) 2339 1399

Re: [Matlab-emacs-discuss] Problem with make command

[Eric L. <eri...@gm...>]

Hi Ollie, I missed your email when you first sent it.  Sorry.

It looks like you have a different flavor of Emacs installed.  To use 
the Makefile, you can do this instead:

make EMACS=spacemacs

or

make EMACS=/path/to/my/emacs

Hopefully that helps you get going!

Eric

On 5/28/20 3:55 PM, Ollie Hulme wrote:
> Dear experts,
>
> I am having issue compiling matlab-emacs via the make command
>
> As instructed, I cd to the matlab-emacs folder, then make yields the 
> following error:
>
> /emacs -batch --no-site-file --eval '(setq debug-on-error t)' -L ./ 
> --eval '(setq generated-autoload-file /
> /"/Users/olliehulme/matlab-emacs/matlab-load.el")' -f 
> batch-update-autoloads /Users/olliehulme/matlab-emacs
> make: emacs: No such file or directory
> make: *** [autoloads] Error 1/
>
> Spacemacs v.0.200.13
>
> Any ideas how i can proceed?
>
> Ollie
>
> -- 
>
>
>
>
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

[Matlab-emacs-discuss] Problem with make command

[Ollie H. <ol...@dr...>]

Dear experts,

I am having issue compiling matlab-emacs via the make command

As instructed, I cd to the matlab-emacs folder, then make yields the
following error:

*emacs -batch --no-site-file --eval '(setq debug-on-error t)' -L ./ --eval
'(setq generated-autoload-file *


*"/Users/olliehulme/matlab-emacs/matlab-load.el")' -f
batch-update-autoloads /Users/olliehulme/matlab-emacsmake: emacs: No such
file or directorymake: *** [autoloads] Error 1*

Spacemacs v.0.200.13

Any ideas how i can proceed?

Ollie

--

[Matlab-emacs-discuss] Running matlab function from emacs by passing arguments

[Kourosh K. <k.k...@gm...>]

Hi,

Does anyone know how I can run matlab function from emacs by passing its 
arguments.  More specifically, I want to be able to run functions with 
C-c C-s (or similar command).

Thanks
Kourosh

[Matlab-emacs-discuss] Question about TAB-completion in edit mode

[Tzu-Yu L. <lee...@gm...>]

Hello,

I am new to emacs and trying to setup emacs for editing matlab files. I 
installed the matlab-mode package from MELPA using spacemacs 
configuration. I managed to have TAB-completion in the matlab edit mode 
by enabling "semantic-mode". However, the completion listing only 
contains the symbols that have been used in the current buffer. I am 
wondering is it possible for the autocompletion to list built-in 
functions from matlab? Am I missing something in my configurations?

The following are the lines that I added in my configuration file:

   (matlab-cedet-setup)
   (add-to-list 'load-path "/usr/local/MATLAB/R2019b/bin")
   (add-hook 'matlab-mode-hook 'auto-complete-mode)

Thanks,

Tzu-Yu

Re: [Matlab-emacs-discuss] MELPA package finally updated

[Eric L. <eri...@gm...>]

Huzzah!  Thanks Uwe.

Eric

On 1/11/20 9:04 AM, Uwe Brauer wrote:
> Hi
>
> I finally managed to submit the patch, which includes all the needed
> subdirectories into the MELPA package, I had to fork, create a branch,
> and then a pull request.
>
> I was just informed that it was merged. So the new, hopefully correct
> MELPA package should be available soon.
>
> Uwe

[Matlab-emacs-discuss] MELPA package finally updated

[Uwe B. <ou...@ma...>]

Hi 

I finally managed to submit the patch, which includes all the needed
subdirectories into the MELPA package, I had to fork, create a branch,
and then a pull request. 

I was just informed that it was merged. So the new, hopefully correct
MELPA package should be available soon.

Uwe 

[Matlab-emacs-discuss] MELPA

[Uwe B. <ou...@ma...>]

Hi 

Although the patch to generate the correct MELPA package is quite
trivial, the procedure to get that patch approved is not.

I have to fork the repository apply by changes and then start  a pull
request. I won't have time to do that before Friday or Saturday, sorry.

Regards

Uwe Brauer 

[Matlab-emacs-discuss] official MELPA package

[Uwe B. <ou...@ma...>]

Hi 

I did not realize that the official MELPA matlab-emacs package is not
complete, thanks to Roman for pointing it out.
The reason is that the MELPA repository needs not only the url where to
fetch it from but also a file, the recipe, which tells MELPA which files
to fetch. Now this recipe file needs to be updated, since the +emacs
directory is not included. I already sent a patch and open a issue in
the MELPA repository but have not heard anything.

I will keep you informed.

Thanks for your patience.

Uwe 

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

[Eric L. <eri...@gm...>]

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 mac_init branch from git, or download the snapshot from this
link: https://sourceforge.net/p/matlab-emacs/src/ci/mac_init/tree/

 Let us know how it goes.
Eric

On Sun, Jan 5, 2020 at 5:18 AM Shervin Safavi <neu...@gm...>
wrote:

> 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 <functionName>” I will receive this error:
>
> Error using edit (line 66)
> Could not find external editor ''
>
> Although this line:
> "emacs.set('clientcmd', 'emacsclient -n -s
> /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-9483');"
> was executed without any error.
>
> I guess there is some issue with executing this line on Mac OS (in general
> or mine specifically):
>
> com.mathworks.services.Prefs.setStringPref('EditorOtherEditor',
> clientcommand);
>
> When I tried to manually change MATLAB preferences (in the native
> platform) to edit files with emacs it doesn't work (won't be open in emacs).
>
> Best,
> Shervin
>
> On Sat, Jan 4, 2020 at 7:56 PM Uwe Brauer <ou...@ma...> wrote:
>
>> >>> "RG" == Roman Garnett <rom...@gm...> 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 not installed by emacs; after checking
>>    > out the repo and manually copying it in, everything seems to be
>>    > working fine.
>>
>> Hi Roman
>>
>> I dig a bit more into it. The recipe file at
>> https://github.com/melpa/melpa/blob/master/recipes/matlab-mode
>>
>> is not correct. I have to see how to fix that but I don't have
>> automatically write access to this file.
>>
>> Regards
>>
>> Uwe
>> _______________________________________________
>> Matlab-emacs-discuss mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>>
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

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

[Shervin S. <neu...@gm...>]

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 <functionName>” I will receive this error:

Error using edit (line 66)
Could not find external editor ''

Although this line:
"emacs.set('clientcmd', 'emacsclient -n -s
/var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-9483');"
was executed without any error.

I guess there is some issue with executing this line on Mac OS (in general
or mine specifically):
            com.mathworks.services.Prefs.setStringPref('EditorOtherEditor',
clientcommand);

When I tried to manually change MATLAB preferences (in the native platform)
to edit files with emacs it doesn't work (won't be open in emacs).

Best,
Shervin

On Sat, Jan 4, 2020 at 7:56 PM Uwe Brauer <ou...@ma...> wrote:

> >>> "RG" == Roman Garnett <rom...@gm...> 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 not installed by emacs; after checking
>    > out the repo and manually copying it in, everything seems to be
>    > working fine.
>
> Hi Roman
>
> I dig a bit more into it. The recipe file at
> https://github.com/melpa/melpa/blob/master/recipes/matlab-mode
>
> is not correct. I have to see how to fix that but I don't have
> automatically write access to this file.
>
> Regards
>
> Uwe
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

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

[Uwe B. <ou...@ma...>]

>>> "RG" == Roman Garnett <rom...@gm...> 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 not installed by emacs; after checking
   > out the repo and manually copying it in, everything seems to be
   > working fine.

Hi Roman

I dig a bit more into it. The recipe file at 
https://github.com/melpa/melpa/blob/master/recipes/matlab-mode

is not correct. I have to see how to fix that but I don't have
automatically write access to this file.

Regards

Uwe 

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

[Uwe B. <ou...@ma...>]

>>> "RG" == Roman Garnett <rom...@gm...> 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 not installed by emacs; after checking
   > out the repo and manually copying it in, everything seems to be
   > working fine.

Hi Roman

Thanks for pointing that out to us. I just cloned 
gi...@gi...:matlab-mode/mirror.git

Which is the base for the MELPA version and in the clone repo
toolbox/+emacs
is present as it should be. 

I will investigate this further and come back as soon as possible.

Uwe 

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

[Roman G. <rom...@gm...>]

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 manually copying it in, everything seems to be
working fine.

Cheers,
Roman

$ emacs --version
GNU Emacs 26.3

$ uname -s -r
Darwin 19.0.0

MELPA package information:

matlab-mode is an installed package.

     Status: Installed in ‘matlab-mode-20191223.2012/’ (unsigned). [Delete]
    Version: 20191223.2012
    Summary: Major mode for MATLAB(R) dot-m files
   Homepage: http://sourceforge.net/projects/matlab-emacs/
   Keywords: [matlab] [programming] [language] [(X)emacs]
Other versions: 20191010.653 (installed), 20180928.1526 (installed),
20191223.2012 (melpa).

On Tue, Dec 31, 2019 at 3:14 PM Eric Ludlam <eri...@gm...> wrote:
>
> 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,
> such as emacsclient.
>
> On linux, you indicate it is setting the preference in emacsinit.  In
> the new version of matlab-emacs, that is now part of emacs.set.  On the
> MAC version, it is trying to run emacs.set (sent from emacs to ML) but
> it doesn't exist. This means one of two things:
>
> 1) Your MAC version is using Emacs code for the new version of
> matlab-emacs, but is using the toolbox directory from the old version of
> matlab-emacs.
> 2) On MAC, emacsinit is failing to set the path so that emacs.set is on
> the path.
>
> If you check your path (ie - 'which emacsinit') and see if there is a
> +emacs directory in the directory where emacsinit is.  I'm assuming it
> is there because emacsinit is calling emacs.Breakpoints and emacs.Stack
> to set up breakpoint and stack managers.
>
> Hope this helps.
> Eric
>
> On 12/28/19 8:37 PM, Shervin Safavi wrote:
> > 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/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-9483');
> >
> > Error is “Unable to resolve the name emacs.set.”
> >
> > I dig into to codes a bit. This is related to the part which we tell
> > MATLAB to use emacs as the editor. So now if type “edit
> > <functionName>” it will be opened in the editor.
> >
> > When I check it on the Linux machine with same version of MATLAB, this
> > functionality is implemented in the “emacsinit” through this line:
> >
> > com.mathworks.services.Prefs.setStringPref('EditorOtherEditor',
> > clientcommand);
> >
> > Where “clientcommand“ is the input to the emacsinit which “emacsclinet
> > -n”. If I do the same thing in the Mac OS doesn’t work, i.e. “edit
> > <functionName>” will open the file in MATLAB editor (of course I also
> > tried server-start on emacs).
> >
> > So I think the issue is in Mac OS we don’t know how to instruct MATLAB
> > to use emac as its editor.
> >
> > Hope that help to solve the issue; otherwise please let me know.
> >
> >  Best,
> > Shervin
> >
> > On Sat, Dec 28, 2019 at 9:36 AM Uwe Brauer <ou...@ma...
> > <mailto:ou...@ma...>> wrote:
> >
> >     >>> "SS" == Shervin Safavi
> >     <neu...@pu...
> >     <mailto:neu...@pu...>>
> >     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 -n -s
> >        >
> >     /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"
> >
> >        > MATLAB version is:
> >
> >        > R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)
> >
> >        > I tried to find the issue by googling and checking the codes
> >     but wasn't
> >        > successful.
> >
> >        > I should note that I set up matlab-mode on a Linux machine
> >     with the same
> >        > version works smoothly.
> >
> >        > If someone has a clue to solve this, please let me know.
> >
> >     Eric, who, for some reason, was not subscribed to the list, got
> >     finally
> >     your email and proposed that you should debug the file emacsinit.m
> >
> >     To quote his email:
> >
> >     ,----
> >     |
> >     |  The emacsinit command should print out "Updating MATLAB path ...".
> >     |
> >     |  If it doesn't then the auto-path update will need to be debugged.
> >     `----
> >
> >      So you can cd to the matlab-emacs-src/toolbox directary, then edit
> >      emacsinit.m, and set a breakpoint at the beginning. Step through and
> >      see why it doesn't add toolbox to the path.
> >
> >     Could you do this and tell us, what you observe?
> >
> >     Thanks
> >
> >     Uwe
> >     _______________________________________________
> >
>
>
>
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

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

[Eric L. <eri...@gm...>]

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, 
such as emacsclient.

On linux, you indicate it is setting the preference in emacsinit.  In 
the new version of matlab-emacs, that is now part of emacs.set.  On the 
MAC version, it is trying to run emacs.set (sent from emacs to ML) but 
it doesn't exist. This means one of two things:

1) Your MAC version is using Emacs code for the new version of 
matlab-emacs, but is using the toolbox directory from the old version of 
matlab-emacs.
2) On MAC, emacsinit is failing to set the path so that emacs.set is on 
the path.

If you check your path (ie - 'which emacsinit') and see if there is a 
+emacs directory in the directory where emacsinit is.  I'm assuming it 
is there because emacsinit is calling emacs.Breakpoints and emacs.Stack 
to set up breakpoint and stack managers.

Hope this helps.
Eric

On 12/28/19 8:37 PM, Shervin Safavi wrote:
> 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/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-9483');
>
> Error is “Unable to resolve the name emacs.set.”
>
> I dig into to codes a bit. This is related to the part which we tell 
> MATLAB to use emacs as the editor. So now if type “edit 
> <functionName>” it will be opened in the editor.
>
> When I check it on the Linux machine with same version of MATLAB, this 
> functionality is implemented in the “emacsinit” through this line:
>
> com.mathworks.services.Prefs.setStringPref('EditorOtherEditor', 
> clientcommand);
>
> Where “clientcommand“ is the input to the emacsinit which “emacsclinet 
> -n”. If I do the same thing in the Mac OS doesn’t work, i.e. “edit 
> <functionName>” will open the file in MATLAB editor (of course I also 
> tried server-start on emacs).
>
> So I think the issue is in Mac OS we don’t know how to instruct MATLAB 
> to use emac as its editor.
>
> Hope that help to solve the issue; otherwise please let me know.
>
>  Best,
> Shervin
>
> On Sat, Dec 28, 2019 at 9:36 AM Uwe Brauer <ou...@ma... 
> <mailto:ou...@ma...>> wrote:
>
>     >>> "SS" == Shervin Safavi
>     <neu...@pu...
>     <mailto:neu...@pu...>>
>     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 -n -s
>        >
>     /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"
>
>        > MATLAB version is:
>
>        > R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)
>
>        > I tried to find the issue by googling and checking the codes
>     but wasn't
>        > successful.
>
>        > I should note that I set up matlab-mode on a Linux machine
>     with the same
>        > version works smoothly.
>
>        > If someone has a clue to solve this, please let me know.
>
>     Eric, who, for some reason, was not subscribed to the list, got
>     finally
>     your email and proposed that you should debug the file emacsinit.m
>
>     To quote his email:
>
>     ,----
>     |
>     |  The emacsinit command should print out "Updating MATLAB path ...".
>     |
>     |  If it doesn't then the auto-path update will need to be debugged.
>     `----
>
>      So you can cd to the matlab-emacs-src/toolbox directary, then edit
>      emacsinit.m, and set a breakpoint at the beginning. Step through and
>      see why it doesn't add toolbox to the path.
>
>     Could you do this and tell us, what you observe?
>
>     Thanks
>
>     Uwe
>     _______________________________________________
>

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

[Shervin S. <neu...@gm...>]

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/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-9483');

Error is “Unable to resolve the name emacs.set.”

I dig into to codes a bit. This is related to the part which we tell MATLAB
to use emacs as the editor. So now if type “edit <functionName>” it will be
opened in the editor.

When I check it on the Linux machine with same version of MATLAB, this
functionality is implemented in the “emacsinit” through this line:

            com.mathworks.services.Prefs.setStringPref('EditorOtherEditor',
clientcommand);

Where “clientcommand“ is the input to the emacsinit which “emacsclinet -n”.
If I do the same thing in the Mac OS doesn’t work, i.e.  “edit
<functionName>” will open the file in MATLAB editor (of course I also tried
server-start on emacs).

So I think the issue is in Mac OS we don’t know how to instruct MATLAB to
use emac as its editor.

Hope that help to solve the issue; otherwise please let me know.

 Best,
Shervin

On Sat, Dec 28, 2019 at 9:36 AM Uwe Brauer <ou...@ma...> wrote:

> >>> "SS" == Shervin Safavi <
> neu...@pu...> 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 -n -s
>    >
> /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"
>
>    > MATLAB version is:
>
>    > R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)
>
>    > I tried to find the issue by googling and checking the codes but
> wasn't
>    > successful.
>
>    > I should note that I set up matlab-mode on a Linux machine with the
> same
>    > version works smoothly.
>
>    > If someone has a clue to solve this, please let me know.
>
> Eric, who, for some reason, was not subscribed to the list, got finally
> your email and proposed that you should debug the file  emacsinit.m
>
> To quote his email:
>
> ,----
> |
> |  The emacsinit command should print out "Updating MATLAB path ...".
> |
> |  If it doesn't then the auto-path update will need to be debugged.
> `----
>
>  So you can cd to the matlab-emacs-src/toolbox directary, then edit
>  emacsinit.m, and set a breakpoint at the beginning. Step through and
>  see why it doesn't add toolbox to the path.
>
> Could you do this and tell us, what you observe?
>
> Thanks
>
> Uwe
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>
-- 
-- for the sake of quick replying/writings is sent from a mobile phone,
with apologies for bad spelling and/or shortness

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

[Uwe B. <ou...@ma...>]

>>> "SS" == Shervin Safavi <neu...@pu...> 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 -n -s
   > /var/folders/r5/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"

   > MATLAB version is:

   > R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)

   > I tried to find the issue by googling and checking the codes but wasn't
   > successful.

   > I should note that I set up matlab-mode on a Linux machine with the same
   > version works smoothly.

   > If someone has a clue to solve this, please let me know.

Eric, who, for some reason, was not subscribed to the list, got finally
your email and proposed that you should debug the file  emacsinit.m

To quote his email:

,----
| 
|  The emacsinit command should print out "Updating MATLAB path ...".
|  
|  If it doesn't then the auto-path update will need to be debugged.
`----
 
 So you can cd to the matlab-emacs-src/toolbox directary, then edit
 emacsinit.m, and set a breakpoint at the beginning. Step through and
 see why it doesn't add toolbox to the path.
 
Could you do this and tell us, what you observe?

Thanks

Uwe 

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

[Uwe B. <ou...@ma...>]

>>> "SS" == Shervin Safavi <neu...@gm...> 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/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"

> MATLAB version is:

> R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)

> I tried to find the issue by googling and checking the codes but wasn't
> successful.

> I should note that I set up matlab-mode on a Linux machine with the same
> version works smoothly.

I am really sorry, I think I tested the new branch quite intensively,
but under Linux (Ubuntu) without any problems. I think Eric either uses
MS Windows or Linux but not Mac. 

Unfortunately we are in the holidays period, so it might take some time
to solve this issue.

If you are acquainted with either git or mercurial, could you try to
bisect this issue[1]? That would be helpful

Regards

Uwe Brauer 

Footnotes:
[1]  that is to found out the latest changeset/commit, which you could
     use without problems.
     https://git-scm.com/docs/git-bisect
     or https://www.mercurial-scm.org/wiki/BisectExtension

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

[Shervin S. <neu...@gm...>]

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/zx0tj5sd3gg3dpynd41gr5s80000gn/T/emacs501/server-28543');"

MATLAB version is:

R2019b Update 1 (9.7.0.1216025) 64-bit (maci64)

I tried to find the issue by googling and checking the codes but wasn't
successful.

I should note that I set up matlab-mode on a Linux machine with the same
version works smoothly.

If someone has a clue to solve this, please let me know.

Best,
Shervin

PS: Sorry if an incomplete version of the email was sent earlier to the
mailing list accidentally.

Re: [Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Uwe B. <ou...@ma...>]

>>> "KC" == Karthik Chikmagalur <kar...@gm...> writes:

   > Update: This bug goes away if I change my m file encoding from
   > utf-8-unix to us-ascii-unix. Matlab's fileread() routine only seems to
   > works correctly if the m-file is encoded as ASCII (and maybe a few
   > other non-UTF8 systems, I'm not sure.) This exception should probably
   > be handled by the code in the function emacsrunregion.

Not sure you got my email, I neither trust gmane nor this list very much
these days.

It seems that Eric Ludlam did not see your email. He pushed a while ago
fix, could you please try it out?

The commit which might fix your problem is f9f7e62367c898b0034483867c524954847733b6

Regards

Uwe 

Re: [Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Uwe B. <ou...@ma...>]

>>> "KC" == Karthik Chikmagalur <kar...@gm...> writes:

> Update: This bug goes away if I change my m file encoding from
> utf-8-unix to us-ascii-unix. Matlab's fileread() routine only seems to
> works correctly if the m-file is encoded as ASCII (and maybe a few
> other non-UTF8 systems, I'm not sure.) This exception should probably
> be handled by the code in the function emacsrunregion.

It seems that Eric Ludlam did not see your email. He pushed a while ago
fix, could you please try it out?

Re: [Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Uwe B. <ou...@ma...>]

>>> "KC" == Karthik Chikmagalur <kar...@pu...> writes:

> Update: This bug goes away if I change my m file encoding from
> utf-8-unix to us-ascii-unix. Matlab's fileread() routine only seems to
> works correctly if the m-file is encoded as ASCII (and maybe a few
> other non-UTF8 systems, I'm not sure.) This exception should probably
> be handled by the code in the function emacsrunregion.

Not sure whether my former email got through. 

The commit which might fix your problem is f9f7e62367c898b0034483867c524954847733b6

Re: [Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Karthik C. <kar...@gm...>]

Update: This bug goes away if I change my m file encoding from utf-8-unix to us-ascii-unix. Matlab's fileread() routine only seems to works correctly if the m-file is encoded as ASCII (and maybe a few other non-UTF8 systems, I'm not sure.) This exception should probably be handled by the code in the function emacsrunregion.

Karthik

Karthik Chikmagalur <kar...@gm...> writes:

> - What is the best way to report bugs pertaining to the modernize
> branch?
>
> - Bug in emacsrunregion.m:
>
> There seems to be a difference in the way Emacs and Matlab count
> characters in my m files. The region I send from Emacs and the region
> being used in the line
>
> ,----
> | ETXT = TXT(startchar:endchar);
> `----
>
> in `emacsrunregion.m' are often (but not always) off by a characters,
> leading to inconsistent behavior and errors.
>
> For example, with this code I wrote in `test.m':
> ,----
> | %% Load mat file with white noise input
> | 
> | load 'white_noise_input.mat'
> | % 
> | % % Use same input for discretized only and discretized+lifted
> | % timesteps_lifted = 16384
> | %% Initialize the lifted system
> | 
> | N = 100;
> | 
> | % Damping coefficient
> | % -------------------
> | damping_coeff = 0.000; % no damping
> | % k = 0.005; %damping coefficient, was 0.005 -> damping ratio = k/(1*omega) = 0.025
> `----
>
> I select the following region and run `matlab-shell-run-region':
>
> ,----
> | %% Initialize the lifted system
> | 
> | N = 100;
> | 
> | % Damping coefficient
> | % -------------------
> | damping_coeff = 0.000; % no damping
> `----
>
> which prints
> ,----
> | >> emacsrunregion('./test.m',164,287)
> `----
>
> This throws a bunch of errors. Here is the region that's actually being
> evaluated (note the same character range):
>
> ,----
> | >> TXT = fileread('./test.m');
> | >> TXT(164:287)
> | 
> | ans =
> | 
> |     '6384
> |      %% Initialize the lifted system
> | 
> |      N = 100;
> | 
> |      % Damping coefficient
> |      % -------------------
> |      damping_coeff = 0.000; % '
> `----
>
> Which is off by a few characters. All my m files are encoded as
> utf-8-unix, if that helps.
>
> - Also, I had a question regarding how `eval' works in Matlab. It
>   appears that it does not maintain state, i.e., eval sets up an
>   environment for execution that it discards once it's done executing
>   the region/line that was sent. This makes interactive Matlab coding
>   (switching back and forth between the m file and `matlab-shell')
>   almost impossible, where in earlier versions the state in
>   `matlab-shell' was persistent. Is this intended behavior?
>
> Karthik Chikmagalur
>
> Uwe Brauer <ou...@ma...> writes:
>
>> Hello everybody
>>
>> * New Branch: modernize 
>>
>> Currently Eric is submitting a lot of changes to the emacs matlab
>> packages. Thanks a lot Eric!
>>
>> Some of the changes/feature which are currently under work have been
>> announced by Eric in a mail to the list, sent at 11 of October.
>>
>> His contributions are committed not to master but to a new branch,
>> called called modernize, so it is not merged into master, yet.
>>
>> I am trying to test his commits, but I would prefer if more users would
>> join me to get a better feedback.
>>
>> Here is what you have to do.
>>
>> * Git users
>>
>> git clone https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-src
>>
>>  git checkout modernize
>>
>> * Mercurial users
>>
>>  install and activate the hg-git plugin
>>
>>  hg clone https://bitbucket.org/durin42/hg-git/
>>  
>>  then in your .hgrc file something like this
>>
>>  hggit = /home/user/src/hg-git/hggit
>>
>> [git]
>> export-additional-refs.named-branch-heads:revset   = head() and not closed()
>> export-additional-refs.named-branch-heads:template = refs/heads/hg_named_branch/{branch}
>>
>>  hg clone https://git.code.sf.net/p/matlab-emacs/src emacs-hg
>>
>>
>>  hg up modernize
>>
>>
>> * Compilation 
>> Run 
>>
>>  make
>>
>> * Set the path
>>
>> Now set the path in your init file, for example 
>>
>> (setq load-path (cons (expand-file-name "~/emacs/site-lisp/packages/src/Matlab/matlab-emacs-src")  load-path))
>>
>> Add 
>>
>> (load-library "matlab-load")
>> (matlab-cedet-setup)
>>
>> Optionality 
>> (semantic-mode 1)
>> (global-semantic-stickyfunc-mode 1)
>> (global-semantic-decoration-mode 1) 
>>
>>
>> * News
>>
>>     1. The debugger works better now, at least this is my impression.
>>
>>     2. matlab-shell-run-cell has been completely rewritten. Now it
>>        possible to have a cell which execute a function, which is
>>        defined at the end of this very same file.
>>
>>     3. Faster load time by moving rarely used content into other files.
>>
>>     4. Support for some older Emacs' has been deleted.
>>
>>     5. Clicking on errors or using next-error in matlab-shell should work better.
>>
>>     6. tab completion in the shell was revamped (but should act mostly
>>        the same)
>>
>>     7. Other bug fixes to editing ML code.
>>
>>
>> Regards
>>
>> Uwe 
>> _______________________________________________
>> Matlab-emacs-discuss mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Karthik C. <kar...@gm...>]

- What is the best way to report bugs pertaining to the modernize
branch?

- Bug in emacsrunregion.m:

There seems to be a difference in the way Emacs and Matlab count
characters in my m files. The region I send from Emacs and the region
being used in the line

,----
| ETXT = TXT(startchar:endchar);
`----

in `emacsrunregion.m' are often (but not always) off by a characters,
leading to inconsistent behavior and errors.

For example, with this code I wrote in `test.m':
,----
| %% Load mat file with white noise input
| 
| load 'white_noise_input.mat'
| % 
| % % Use same input for discretized only and discretized+lifted
| % timesteps_lifted = 16384
| %% Initialize the lifted system
| 
| N = 100;
| 
| % Damping coefficient
| % -------------------
| damping_coeff = 0.000; % no damping
| % k = 0.005; %damping coefficient, was 0.005 -> damping ratio = k/(1*omega) = 0.025
`----

I select the following region and run `matlab-shell-run-region':

,----
| %% Initialize the lifted system
| 
| N = 100;
| 
| % Damping coefficient
| % -------------------
| damping_coeff = 0.000; % no damping
`----

which prints
,----
| >> emacsrunregion('./test.m',164,287)
`----

This throws a bunch of errors. Here is the region that's actually being
evaluated (note the same character range):

,----
| >> TXT = fileread('./test.m');
| >> TXT(164:287)
| 
| ans =
| 
|     '6384
|      %% Initialize the lifted system
| 
|      N = 100;
| 
|      % Damping coefficient
|      % -------------------
|      damping_coeff = 0.000; % '
`----

Which is off by a few characters. All my m files are encoded as
utf-8-unix, if that helps.

- Also, I had a question regarding how `eval' works in Matlab. It
  appears that it does not maintain state, i.e., eval sets up an
  environment for execution that it discards once it's done executing
  the region/line that was sent. This makes interactive Matlab coding
  (switching back and forth between the m file and `matlab-shell')
  almost impossible, where in earlier versions the state in
  `matlab-shell' was persistent. Is this intended behavior?

Karthik Chikmagalur

Uwe Brauer <ou...@ma...> writes:

> Hello everybody
>
> * New Branch: modernize 
>
> Currently Eric is submitting a lot of changes to the emacs matlab
> packages. Thanks a lot Eric!
>
> Some of the changes/feature which are currently under work have been
> announced by Eric in a mail to the list, sent at 11 of October.
>
> His contributions are committed not to master but to a new branch,
> called called modernize, so it is not merged into master, yet.
>
> I am trying to test his commits, but I would prefer if more users would
> join me to get a better feedback.
>
> Here is what you have to do.
>
> * Git users
>
> git clone https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-src
>
>  git checkout modernize
>
> * Mercurial users
>
>  install and activate the hg-git plugin
>
>  hg clone https://bitbucket.org/durin42/hg-git/
>  
>  then in your .hgrc file something like this
>
>  hggit = /home/user/src/hg-git/hggit
>
> [git]
> export-additional-refs.named-branch-heads:revset   = head() and not closed()
> export-additional-refs.named-branch-heads:template = refs/heads/hg_named_branch/{branch}
>
>  hg clone https://git.code.sf.net/p/matlab-emacs/src emacs-hg
>
>
>  hg up modernize
>
>
> * Compilation 
> Run 
>
>  make
>
> * Set the path
>
> Now set the path in your init file, for example 
>
> (setq load-path (cons (expand-file-name "~/emacs/site-lisp/packages/src/Matlab/matlab-emacs-src")  load-path))
>
> Add 
>
> (load-library "matlab-load")
> (matlab-cedet-setup)
>
> Optionality 
> (semantic-mode 1)
> (global-semantic-stickyfunc-mode 1)
> (global-semantic-decoration-mode 1) 
>
>
> * News
>
>     1. The debugger works better now, at least this is my impression.
>
>     2. matlab-shell-run-cell has been completely rewritten. Now it
>        possible to have a cell which execute a function, which is
>        defined at the end of this very same file.
>
>     3. Faster load time by moving rarely used content into other files.
>
>     4. Support for some older Emacs' has been deleted.
>
>     5. Clicking on errors or using next-error in matlab-shell should work better.
>
>     6. tab completion in the shell was revamped (but should act mostly
>        the same)
>
>     7. Other bug fixes to editing ML code.
>
>
> Regards
>
> Uwe 
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

[Matlab-emacs-discuss] Call for testers, code not in master (yet)

[Uwe B. <ou...@ma...>]

Hello everybody

* New Branch: modernize 

Currently Eric is submitting a lot of changes to the emacs matlab
packages. Thanks a lot Eric!

Some of the changes/feature which are currently under work have been
announced by Eric in a mail to the list, sent at 11 of October.

His contributions are committed not to master but to a new branch,
called called modernize, so it is not merged into master, yet.

I am trying to test his commits, but I would prefer if more users would
join me to get a better feedback.

Here is what you have to do.

* Git users

git clone https://git.code.sf.net/p/matlab-emacs/src matlab-emacs-src

 git checkout modernize

* Mercurial users

 install and activate the hg-git plugin

 hg clone https://bitbucket.org/durin42/hg-git/
 
 then in your .hgrc file something like this

 hggit = /home/user/src/hg-git/hggit

[git]
export-additional-refs.named-branch-heads:revset   = head() and not closed()
export-additional-refs.named-branch-heads:template = refs/heads/hg_named_branch/{branch}

 hg clone https://git.code.sf.net/p/matlab-emacs/src emacs-hg


 hg up modernize


* Compilation 
Run 

 make

* Set the path

Now set the path in your init file, for example 

(setq load-path (cons (expand-file-name "~/emacs/site-lisp/packages/src/Matlab/matlab-emacs-src")  load-path))

Add 

(load-library "matlab-load")
(matlab-cedet-setup)

Optionality 
(semantic-mode 1)
(global-semantic-stickyfunc-mode 1)
(global-semantic-decoration-mode 1) 


* News

    1. The debugger works better now, at least this is my impression.

    2. matlab-shell-run-cell has been completely rewritten. Now it
       possible to have a cell which execute a function, which is
       defined at the end of this very same file.

    3. Faster load time by moving rarely used content into other files.

    4. Support for some older Emacs' has been deleted.

    5. Clicking on errors or using next-error in matlab-shell should work better.

    6. tab completion in the shell was revamped (but should act mostly
       the same)

    7. Other bug fixes to editing ML code.


Regards

Uwe