matlab-emacs-discuss — Discuss Emacs/MATLAB integration

Re: [Matlab-emacs-discuss] bug in formatting of comments in "methods" blocks

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

Hi,

It looks like it thinks your comment is an end-of-function comment.  The following update fixes the issue for me:

(defun matlab-ltype-endfunction-comm ()
  "Return t if the current line is an ENDFUNCTION style comment."
  (save-excursion
    (if (not (matlab-ltype-comm))
	nil
      (beginning-of-line)
      (if (looking-at "^[ \t]*%[ \t]*endfunction")
	  t
	(while (and (or (matlab-ltype-comm)
			(matlab-ltype-empty))
		    (not (eobp)))
	  (forward-line 1))
	(and (matlab-ltype-function-definition)
	     (not (save-excursion (matlab-beginning-of-enclosing-defun))))
	))))

Basically, the last line checks to see if the defun is enclosed in some other structure.

What I don't know is if it will break anything else. :(

Eric



-----------------------------
From: Nick Henderson [mailto:nw...@st...] 
Sent: Thursday, July 07, 2011 11:22 PM
To: mat...@li...
Subject: [Matlab-emacs-discuss] bug in formatting of comments in "methods" blocks

Hello All,

There seems to be a bug in the formatting of comments in methods blocks.  See the file attached file, bug1.m.  The first comment in the methods block causes formatting to be messed up.  If it is removed, things work as they should.

The strange thing is that comments in the classdef and properties block work just fine.

Cheers,
Nick

-- 
nw...@st...
nic...@gm...
650-352-3551

[Matlab-emacs-discuss] bug in formatting of comments in "methods" blocks

[Nick H. <nw...@st...>]

Hello All,

There seems to be a bug in the formatting of comments in methods blocks.
 See the file attached file, bug1.m.  The first comment in the methods block
causes formatting to be messed up.  If it is removed, things work as they
should.

The strange thing is that comments in the classdef and properties block work
just fine.

Cheers,
Nick

-- 
nw...@st...
nic...@gm...
650-352-3551

[Matlab-emacs-discuss] matlab edit command

[Cheng W. <cry...@gm...>]

Hi guys,

I've fixed it by setting the external editor option in 'Preference'.

Thanks for your patience!

Cheng

[Matlab-emacs-discuss] matlab edit command

[Cheng W. <cry...@gm...>]

Hi guys,

I've been using matlab mode for emacs for quite some time. When I move to
ubuntu 11.04 from 10.10, I find when you type the 'edit' function in
matlab-shell will not open a new buffer anymore. So it's not possible to
edit old m files which are in matlab path without C-x C-f. I'm not sure
where is the problem and hope someone could give me some hints.

As I just use this mode for editing, so the relevant configuration in my
.emacs looks like this.
;; ------------------------------------------------------------
;; matlab
;; ------------------------------------------------------------
; after adding path
(load-library "matlab-load")

The current emacs version is 23.2.1, I don't remember what was the version
in 10.10 and 10.04, maybe 23.0.

The matlab.el is the same as before.
 matlab-mode-version "3.3.1"


Thank you very much for you attention!

Cheng

Re: [Matlab-emacs-discuss] Launch matlab in new frame ?

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

Hi,

Sorry for the very tardy response.

You can always put MATLAB into a new frame by doing "C-x 5 2" and put the *MATLAB* buffer into that frame.

In matlab.el, look for a call to 'display-buffer'.  In Emacs 23.2 at least, the 3rd input argument specifies the frame, so you could change that line to:

      (display-buffer msbn nil "visible"))

around line 5034 to fix it for the cell case.  save-and-go seems to do something similar already.

I don't understand the issue w/ the comment character you mention.  The only parts that change are values in strings, so I don't see how the % could affect anything.

Eric

-----Original Message-----
From: Laurent Jacques [mailto:lau...@uc...] 
Sent: Monday, May 16, 2011 3:45 AM
To: mat...@li...
Subject: [Matlab-emacs-discuss] Launch matlab in new frame ?

Dear all,

I have few requests on this great emacs-matlab mode.

Do you you know if:

- it is possible to launch matlab in a new emacs *frame* (rather than in a sub-window) and then prevent emacs to still reopen a new matlab sub-window (split
window) when a mfile cell is run (with "run cell").
I'd like to see "run cell" call the frame where matlab is inside.

- to program in LISP the "run current cell and jump to next" ?


Last point about svn:

In the last matlab.el of the SVN, the "run cell" is bugged (at least on my Carbon emacs running on Mac).

All lines are concatenated into a big line before to be run in matlab.

This cause a bug if at least one line of the cell has a "%" comment, i.e., all the text after it is considered as a comment by matlab.
I had to go back to a previous version of matlab.el to solve this issue.

Best regards,
Laurent

--
Dr. Laurent JACQUES
Postdoctoral Researcher, Return Grant, BELSPO, Belgium

Institute of Information and Communication Technologies,
	Electronics and Applied Mathematics (ICTEAM-TELE) University of Louvain Batiment Stévin Place du Levant 2, PO Box L5.04.01
1348 Louvain-la-Neuve, Belgium

Office: a.133
Tel: +32 10 47 81 24
Fax: +32 10 47 20 89
http://perso.uclouvain.be/laurent.jacques


------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Matlab-emacs-discuss mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

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

Thanks for the feedback.

I've added a variant of my original simple suggestion into CVS.

Users can shut-off the HTML stuff by typing the following into MATLAB after it starts:

    feature('HotLinks','off');

This won't catch all the hot-links, and shutting off the rendering via your matlab-shell-mode-hook with code like this:

  (remove-hook 'comint-output-filter-functions 'matlab-shell-render-html-anchor t)
  (remove-hook 'comint-output-filter-functions 'matlab-shell-render-errors-as-anchor t)

will result in some random messy html text in your buffer.

Eric

From: Ondra Kamenik [mailto:ond...@gm...]
Sent: Thursday, June 16, 2011 5:27 AM
To: Eric Ludlam
Cc: mat...@li...
Subject: Re: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

Eric,

I changed the line in matlab-shell-render-html-anchor as you suggested and emacs does not slow down. Many Thanks!

If you plan to address this in more systematic way, what about allowing the user to switch off html rendering completely?

Many thanks again!

Ondra K.


On Tue, Jun 14, 2011 at 4:34 PM, Eric Ludlam <Eri...@ma...<mailto:Eri...@ma...>> wrote:
Hi,

There were some bugs I fixed a while back relating to highlighting error messages so they are clickable, and can go to the source of the error.  That could be the issue, since that code will look backwards to fixup boken error messages.  Error text is broken if ½ comes out on the command line in one chunk, followed by another chunk later.  When the second chunk comes out, you need to look back for the beginning of the chunk.

Since you already directly know it is size related, you could set  comint-buffer-maximum-size in your matlab-shell-mode-hook for a quick fix.

In matlab-shell functions, I see 1 occurrence of re-search-backward with no bounds.  (The second argument.)  One is in matlab-shell-render-html-anchor.  I'll guess it needs something similar to what is in matlab-shell-render-errors-as-anchor with that reverse search.   It may be that the error and html highlighters should share a single variable to mark the last location of an error.

Anyway, as a quick hack,  line 4522 (in the CVS version of matlab.el in the function matlab-shell-render-anchor) could be

(when (re-search-backward matlab-anchor-beg (max 0 (- (point-max) 5000) t)

just to put some random limit for performance testing.  If that helps, we'll know what the issue is and can fix it more robustly.

Eric

From: Ondra Kamenik [mailto:ond...@gm...<mailto:ond...@gm...>]
Sent: Tuesday, June 14, 2011 10:02 AM
To: mat...@li...<mailto:mat...@li...>
Subject: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

Eric and others,

I have been a happy user of matlab-shell for years. Thanks Eric.

However, recently (I cannot recollect exactly when, one year ago?), I experience slowing down of matlab-shell. We run complex matlab programs which call various external programs. The output displayed in matlab-shell consists of messages of various format from matlab, latex, svn, rational expectations solvers, etc. It seems that if there is a lot of output in the matlab-shell buffer, emacs becomes unresponsive, or very slow. Looking at top output, emacs seems to take much of processor time doing effectively nothing. The situation seems to be worse, if there are some matlab errors in the output.

It seems to me that emacs does some processing of the whole buffer each time something happens on the command line. When the buffer gets large (say 20000 lines), emacs seems very busy (by processing the whole buffer?) and the interactive work becomes a real pain. If one executes the code in M-file using C-c r, it takes ages before the code is copied to the buffer and one can actually observe how the code is being added character by c-h-a-r-a-c-t-e-r.

If you tell me how I can debug it, I will be happy to replicate the behaviour and send you a further information.

I use matlab 2009b, various computers with fedora 12 through 14, emacs version 23.2.1 or 23.1.1, matlab-shell version 3.3.1 or 3.3.0. My colleague has the same problem on some ubuntu with newer matlab. On my fedora 12, emacs 23.1.1 and matlab shell 3.3.1 laptop, I do not experience the problem. On my desktop with the same versions I have the problem. The only difference I am aware of is that the laptop is 64, desktop is 32. But my other desktop is 64 and I have the error there.

I will be happy to provide you with more information if I know what.

Thanks!

Ondra K.

Re: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

[Ondra K. <ond...@gm...>]

Eric,

I changed the line in matlab-shell-render-html-anchor as you suggested and
emacs does not slow down. Many Thanks!

If you plan to address this in more systematic way, what about allowing the
user to switch off html rendering completely?

Many thanks again!

Ondra K.



On Tue, Jun 14, 2011 at 4:34 PM, Eric Ludlam <Eri...@ma...>wrote:

>  Hi,****
>
> ** **
>
> There were some bugs I fixed a while back relating to highlighting error
> messages so they are clickable, and can go to the source of the error.  That
> could be the issue, since that code will look backwards to fixup boken error
> messages.  Error text is broken if ½ comes out on the command line in one
> chunk, followed by another chunk later.  When the second chunk comes out,
> you need to look back for the beginning of the chunk.****
>
> ** **
>
> Since you already directly know it is size related, you could set
> comint-buffer-maximum-size in your matlab-shell-mode-hook for a quick fix.
> ****
>
> ** **
>
> In matlab-shell functions, I see 1 occurrence of re-search-backward with no
> bounds.  (The second argument.)  One is in matlab-shell-render-html-anchor.
> I’ll guess it needs something similar to what is in
> matlab-shell-render-errors-as-anchor with that reverse search.   It may be
> that the error and html highlighters should share a single variable to mark
> the last location of an error.****
>
> ** **
>
> Anyway, as a quick hack,  line 4522 (in the CVS version of matlab.el in the
> function matlab-shell-render-anchor) could be****
>
> ** **
>
> (when (re-search-backward matlab-anchor-beg (max 0 (- (point-max) 5000) t)
> ****
>
> ** **
>
> just to put some random limit for performance testing.  If that helps,
> we’ll know what the issue is and can fix it more robustly.****
>
> ** **
>
> Eric****
>
> ** **
>
> *From:* Ondra Kamenik [mailto:ond...@gm...]
> *Sent:* Tuesday, June 14, 2011 10:02 AM
> *To:* mat...@li...
> *Subject:* [Matlab-emacs-discuss] matlab-shell slows down when buffer is
> large****
>
> ** **
>
> Eric and others,
>
> I have been a happy user of matlab-shell for years. Thanks Eric.
>
> However, recently (I cannot recollect exactly when, one year ago?), I
> experience slowing down of matlab-shell. We run complex matlab programs
> which call various external programs. The output displayed in matlab-shell
> consists of messages of various format from matlab, latex, svn, rational
> expectations solvers, etc. It seems that if there is a lot of output in the
> matlab-shell buffer, emacs becomes unresponsive, or very slow. Looking at
> top output, emacs seems to take much of processor time doing effectively
> nothing. The situation seems to be worse, if there are some matlab errors in
> the output.
>
> It seems to me that emacs does some processing of the whole buffer each
> time something happens on the command line. When the buffer gets large (say
> 20000 lines), emacs seems very busy (by processing the whole buffer?) and
> the interactive work becomes a real pain. If one executes the code in M-file
> using C-c r, it takes ages before the code is copied to the buffer and one
> can actually observe how the code is being added character by
> c-h-a-r-a-c-t-e-r.
>
> If you tell me how I can debug it, I will be happy to replicate the
> behaviour and send you a further information.
>
> I use matlab 2009b, various computers with fedora 12 through 14, emacs
> version 23.2.1 or 23.1.1, matlab-shell version 3.3.1 or 3.3.0. My colleague
> has the same problem on some ubuntu with newer matlab. On my fedora 12,
> emacs 23.1.1 and matlab shell 3.3.1 laptop, I do not experience the problem.
> On my desktop with the same versions I have the problem. The only difference
> I am aware of is that the laptop is 64, desktop is 32. But my other desktop
> is 64 and I have the error there.
>
> I will be happy to provide you with more information if I know what.
>
> Thanks!
>
> Ondra K.****
>

Re: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

[Ondra K. <ond...@gm...>]

Many thanks. I will check it out.

Ondra K.
Sent from my wireless handheld
 On Jun 14, 2011 4:34 PM, "Eric Ludlam" <Eri...@ma...> wrote:
> Hi,
>
> There were some bugs I fixed a while back relating to highlighting error
messages so they are clickable, and can go to the source of the error. That
could be the issue, since that code will look backwards to fixup boken error
messages. Error text is broken if ½ comes out on the command line in one
chunk, followed by another chunk later. When the second chunk comes out, you
need to look back for the beginning of the chunk.
>
> Since you already directly know it is size related, you could set
comint-buffer-maximum-size in your matlab-shell-mode-hook for a quick fix.
>
> In matlab-shell functions, I see 1 occurrence of re-search-backward with
no bounds. (The second argument.) One is in matlab-shell-render-html-anchor.
I'll guess it needs something similar to what is in
matlab-shell-render-errors-as-anchor with that reverse search. It may be
that the error and html highlighters should share a single variable to mark
the last location of an error.
>
> Anyway, as a quick hack, line 4522 (in the CVS version of matlab.el in the
function matlab-shell-render-anchor) could be
>
> (when (re-search-backward matlab-anchor-beg (max 0 (- (point-max) 5000) t)
>
> just to put some random limit for performance testing. If that helps,
we'll know what the issue is and can fix it more robustly.
>
> Eric
>
> From: Ondra Kamenik [mailto:ond...@gm...]
> Sent: Tuesday, June 14, 2011 10:02 AM
> To: mat...@li...
> Subject: [Matlab-emacs-discuss] matlab-shell slows down when buffer is
large
>
> Eric and others,
>
> I have been a happy user of matlab-shell for years. Thanks Eric.
>
> However, recently (I cannot recollect exactly when, one year ago?), I
experience slowing down of matlab-shell. We run complex matlab programs
which call various external programs. The output displayed in matlab-shell
consists of messages of various format from matlab, latex, svn, rational
expectations solvers, etc. It seems that if there is a lot of output in the
matlab-shell buffer, emacs becomes unresponsive, or very slow. Looking at
top output, emacs seems to take much of processor time doing effectively
nothing. The situation seems to be worse, if there are some matlab errors in
the output.
>
> It seems to me that emacs does some processing of the whole buffer each
time something happens on the command line. When the buffer gets large (say
20000 lines), emacs seems very busy (by processing the whole buffer?) and
the interactive work becomes a real pain. If one executes the code in M-file
using C-c r, it takes ages before the code is copied to the buffer and one
can actually observe how the code is being added character by
c-h-a-r-a-c-t-e-r.
>
> If you tell me how I can debug it, I will be happy to replicate the
behaviour and send you a further information.
>
> I use matlab 2009b, various computers with fedora 12 through 14, emacs
version 23.2.1 or 23.1.1, matlab-shell version 3.3.1 or 3.3.0. My colleague
has the same problem on some ubuntu with newer matlab. On my fedora 12,
emacs 23.1.1 and matlab shell 3.3.1 laptop, I do not experience the problem.
On my desktop with the same versions I have the problem. The only difference
I am aware of is that the laptop is 64, desktop is 32. But my other desktop
is 64 and I have the error there.
>
> I will be happy to provide you with more information if I know what.
>
> Thanks!
>
> Ondra K.

Re: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

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

Hi,

There were some bugs I fixed a while back relating to highlighting error messages so they are clickable, and can go to the source of the error.  That could be the issue, since that code will look backwards to fixup boken error messages.  Error text is broken if ½ comes out on the command line in one chunk, followed by another chunk later.  When the second chunk comes out, you need to look back for the beginning of the chunk.

Since you already directly know it is size related, you could set  comint-buffer-maximum-size in your matlab-shell-mode-hook for a quick fix.

In matlab-shell functions, I see 1 occurrence of re-search-backward with no bounds.  (The second argument.)  One is in matlab-shell-render-html-anchor.  I'll guess it needs something similar to what is in matlab-shell-render-errors-as-anchor with that reverse search.   It may be that the error and html highlighters should share a single variable to mark the last location of an error.

Anyway, as a quick hack,  line 4522 (in the CVS version of matlab.el in the function matlab-shell-render-anchor) could be

(when (re-search-backward matlab-anchor-beg (max 0 (- (point-max) 5000) t)

just to put some random limit for performance testing.  If that helps, we'll know what the issue is and can fix it more robustly.

Eric

From: Ondra Kamenik [mailto:ond...@gm...]
Sent: Tuesday, June 14, 2011 10:02 AM
To: mat...@li...
Subject: [Matlab-emacs-discuss] matlab-shell slows down when buffer is large

Eric and others,

I have been a happy user of matlab-shell for years. Thanks Eric.

However, recently (I cannot recollect exactly when, one year ago?), I experience slowing down of matlab-shell. We run complex matlab programs which call various external programs. The output displayed in matlab-shell consists of messages of various format from matlab, latex, svn, rational expectations solvers, etc. It seems that if there is a lot of output in the matlab-shell buffer, emacs becomes unresponsive, or very slow. Looking at top output, emacs seems to take much of processor time doing effectively nothing. The situation seems to be worse, if there are some matlab errors in the output.

It seems to me that emacs does some processing of the whole buffer each time something happens on the command line. When the buffer gets large (say 20000 lines), emacs seems very busy (by processing the whole buffer?) and the interactive work becomes a real pain. If one executes the code in M-file using C-c r, it takes ages before the code is copied to the buffer and one can actually observe how the code is being added character by c-h-a-r-a-c-t-e-r.

If you tell me how I can debug it, I will be happy to replicate the behaviour and send you a further information.

I use matlab 2009b, various computers with fedora 12 through 14, emacs version 23.2.1 or 23.1.1, matlab-shell version 3.3.1 or 3.3.0. My colleague has the same problem on some ubuntu with newer matlab. On my fedora 12, emacs 23.1.1 and matlab shell 3.3.1 laptop, I do not experience the problem. On my desktop with the same versions I have the problem. The only difference I am aware of is that the laptop is 64, desktop is 32. But my other desktop is 64 and I have the error there.

I will be happy to provide you with more information if I know what.

Thanks!

Ondra K.

[Matlab-emacs-discuss] matlab-shell slows down when buffer is large

[Ondra K. <ond...@gm...>]

Eric and others,

I have been a happy user of matlab-shell for years. Thanks Eric.

However, recently (I cannot recollect exactly when, one year ago?), I
experience slowing down of matlab-shell. We run complex matlab programs
which call various external programs. The output displayed in matlab-shell
consists of messages of various format from matlab, latex, svn, rational
expectations solvers, etc. It seems that if there is a lot of output in the
matlab-shell buffer, emacs becomes unresponsive, or very slow. Looking at
top output, emacs seems to take much of processor time doing effectively
nothing. The situation seems to be worse, if there are some matlab errors in
the output.

It seems to me that emacs does some processing of the whole buffer each time
something happens on the command line. When the buffer gets large (say 20000
lines), emacs seems very busy (by processing the whole buffer?) and the
interactive work becomes a real pain. If one executes the code in M-file
using C-c r, it takes ages before the code is copied to the buffer and one
can actually observe how the code is being added character by
c-h-a-r-a-c-t-e-r.

If you tell me how I can debug it, I will be happy to replicate the
behaviour and send you a further information.

I use matlab 2009b, various computers with fedora 12 through 14, emacs
version 23.2.1 or 23.1.1, matlab-shell version 3.3.1 or 3.3.0. My colleague
has the same problem on some ubuntu with newer matlab. On my fedora 12,
emacs 23.1.1 and matlab shell 3.3.1 laptop, I do not experience the problem.
On my desktop with the same versions I have the problem. The only difference
I am aware of is that the laptop is 64, desktop is 32. But my other desktop
is 64 and I have the error there.

I will be happy to provide you with more information if I know what.

Thanks!

Ondra K.

Re: [Matlab-emacs-discuss] Comments right after 'methods'-statement in class definition mess up indentation

[<rp...@gm...>]

On Tue, Jun 7, 2011 at 5:25 PM,  <rp...@gm...> wrote:
> On Tue, Jun 7, 2011 at 4:38 PM, Daniele Nicolodi <da...@gr...> wrote:
>> On 07/06/11 15:06, rp...@gm... wrote:
>>> Hello everyone,
>>>
>>> I noticed that when I insert a commented line right after the
>>> 'methods'-statement in a class definition, the indentation fails
>>> (starting at the comment, the indentation is reset to the beginning of
>>> the line).
>>
>> Hello,
>>
>> I fixed a couple of bugs regarding comments indentation, especially help
>> strings, in my copy of matlab-mode (I haven't found the time yet to send
>> patches upstream).
>>
>> I'm not sure I following your description. Can you please provide a
>> simple example of the problem you are experiencing, including the
>> indentation you obtain from matlab-mode and the desired one?
>>
>> The solution should not be too difficult and I may found the time to
>> look at it soon.
>>
>> Cheers,
>> --
>> Daniele
>>
>
> Hi Daniele,
>
> thanks for your help. What I would like to see is the following:
>
> classdef myclass
>     methods
>           %> comment style I use
>           function some = function(thing)
>                some = thing
>           end
>     end
> end
>
> what I get is this:
>
> classdef myclass
>     methods
> %> comment is indented to beginning of line
> function some = function(thing)
>    % but relative indentation in class still works
>     some = thing
> end
> end
> end
>
> This reproduces *most* of the time, but not always. I just came to
> think that the issue might be that these files originally come from a
> windows machine and this actually might be a
> carriage-return-problem...
>
> best
> Hans
>

I looked into the problem of different line endings on windows & linux
- however, the problem appears also on files generated on linux. The
problem must thus lie with matlab.el. Note that I have only observed
this with the methods-keyword - comments+indentation after the
properties-keyword work perfectly fine.

Hans

Re: [Matlab-emacs-discuss] Comments right after 'methods'-statement in class definition mess up indentation

[Daniele N. <da...@gr...>]

On 07/06/11 15:06, rp...@gm... wrote:
> Hello everyone,
> 
> I noticed that when I insert a commented line right after the
> 'methods'-statement in a class definition, the indentation fails
> (starting at the comment, the indentation is reset to the beginning of
> the line).

Hello,

I fixed a couple of bugs regarding comments indentation, especially help
strings, in my copy of matlab-mode (I haven't found the time yet to send
patches upstream).

I'm not sure I following your description. Can you please provide a
simple example of the problem you are experiencing, including the
indentation you obtain from matlab-mode and the desired one?

The solution should not be too difficult and I may found the time to
look at it soon.

Cheers,
-- 
Daniele

[Matlab-emacs-discuss] Comments right after 'methods'-statement in class definition mess up indentation

[<rp...@gm...>]

Hello everyone,

I noticed that when I insert a commented line right after the
'methods'-statement in a class definition, the indentation fails
(starting at the comment, the indentation is reset to the beginning of
the line).

Does anyone else observe this behaviour?

This may seem as a side-issue, but I am trying to use a documentation
generator (http://www.mathworks.com/matlabcentral/fileexchange/25925-using-doxygen-with-matlab)
that needs the describing comment above the function definition.

The weird thing is that it works just fine for the properties-keyword.

Any help is greatly appreciated

Thanks
Hans

[Matlab-emacs-discuss] Launch matlab in new frame ?

[Laurent J. <lau...@uc...>]

Dear all,

I have few requests on this great emacs-matlab mode.

Do you you know if:

- it is possible to launch matlab in a new emacs *frame* (rather than in 
a sub-window)
and then prevent emacs to still reopen a new matlab sub-window (split 
window) when a mfile cell is run (with "run cell").
I'd like to see "run cell" call the frame where matlab is inside.

- to program in LISP the "run current cell and jump to next" ?


Last point about svn:

In the last matlab.el of the SVN, the "run cell" is bugged (at least on 
my Carbon emacs running on Mac).

All lines are concatenated into a big line before to be run in matlab.

This cause a bug if at least one line of the cell has a "%" comment, 
i.e., all the text after it is considered as a comment by matlab.
I had to go back to a previous version of matlab.el to solve this issue.

Best regards,
Laurent

-- 
Dr. Laurent JACQUES
Postdoctoral Researcher, Return Grant, BELSPO, Belgium

Institute of Information and Communication Technologies,
	Electronics and Applied Mathematics (ICTEAM-TELE)
University of Louvain
Batiment Stévin
Place du Levant 2, PO Box L5.04.01
1348 Louvain-la-Neuve, Belgium

Office: a.133
Tel: +32 10 47 81 24
Fax: +32 10 47 20 89
http://perso.uclouvain.be/laurent.jacques

Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

[Alan <ora...@gm...>]

I just tried your Revision 1.30, and it works with no errors on doing
'emacs blah.m', or loading a .m file with an already open emacs.

Thanks for the fix!

You're right that the error I got with Rev 1.29 was different from
before. With Revision 1.29, I got:

"File mode specification error: (void-variable mlfile)"

Whereas with Revisions <= 1.28, but >= 1.14, I got:

"File mode specification error: (wrong-type-argument stringp nil)"

Debug output for this is:

Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  file-name-directory(nil)
  (expand-file-name "toolbox/emacsinit.m" (file-name-directory
(locate-library "matlab")))
  (let ((dir ...)) (file-exists-p dir))
  (defvar matlab-shell-use-emacs-toolbox (let (...) (file-exists-p
dir)) "Add the `matlab-shell' MATLAB toolbox to the MATLAB path on
startup.")
  eval-buffer(#<buffer  *load*> nil "/home/alan/matlab.el" nil t)  ;
Reading at buffer position 152834
  load-with-code-conversion("/home/alan/matlab.el" "/home/alan/matlab.el" nil t)
  matlab-mode()
  set-auto-mode-0(matlab-mode nil)
  set-auto-mode()
  normal-mode(t)
  after-find-file(t t)
  find-file-noselect-1(#<buffer blah.m> "~/blah.m" nil nil "~/blah.m" nil)
  find-file-noselect("~/blah.m" nil nil t)
  find-file("~/blah.m" t)
  call-interactively(find-file nil nil)


But both these errors have gone away with Rev 1.30.


On Wed, Mar 23, 2011 at 3:30 PM, Eric Ludlam <Eri...@ma...> wrote:
> I was able to reproduce this explicitly when I executed the code by hand, but for some reason it didn't show up when I loaded in matlab files which is how that got checked in today.  I fixed it and checked it in.
>
> I don't know if that fixed your original issue since the error is different, and you didn't have that patch when you had the stringp issue.
>
> Eric
>
> -----Original Message-----
> From: Alan [mailto:ora...@gm...]
> Sent: Wednesday, March 23, 2011 2:56 PM
> To: mat...@li...
> Subject: Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)
>
> I just realized I forgot to CC the email list. Here is the reply I
> sent to Eric. Sorry to Eric for getting 2 emails!
>
> Thanks for the reply.
>
> Using the latest matlab.el (Revision 1.29), here is the output after
> starting 'emacs -nw', then doing M-x toggle-debug-on-error, then C-x
> C-f blah.m to create or find a non-existent text file "blah.m":
>
> Debugger entered--Lisp error: (void-variable mlfile)
>  (or mlfile "")
>  (file-name-directory (or mlfile ""))
>  (expand-file-name "toolbox/emacsinit.m" (file-name-directory (or mlfile "")))
>  (let ((mlfile ...) (dir ...)) (and mlfile (file-exists-p dir)))
>  (defvar matlab-shell-use-emacs-toolbox (let (... ...) (and
> mlfile...)) "Add the `matlab-shell' MATLAB toolbox to the MATLAB path
> on startup.")
>  eval-buffer(#<buffer  *load*> nil "/home/alan/.matlab.el" nil t)  ;
> Reading at buffer position 152939
>  load-with-code-conversion("/home/alan/.matlab.el"
> "/home/alan/.matlab.el" nil t)
>  matlab-mode()
>  set-auto-mode-0(matlab-mode nil)
>  set-auto-mode()
>  normal-mode(t)
>  after-find-file(t t)
>  find-file-noselect-1(#<buffer blah.m> "~/blah.m" nil nil "~/blah.m" nil)
>  find-file-noselect("~/blah.m" nil nil t)
>  find-file("~/blah.m" t)
>  call-interactively(find-file nil nil)
>
>
> Some further info about my setup: I renamed the file matlab.el to
> .matlab.el, and used the following code in my .emacs file:
>
> (autoload 'matlab-mode "~/.matlab" "Enter MATLAB mode." t)
> (setq auto-mode-alist (cons '("\\.m\\'" . matlab-mode)
> auto-mode-alist))
> (autoload 'matlab-shell "~/.matlab" "Interactive MATLAB mode." t)
>
>
> Any suggestions or hints?
>
> Thanks,
> Alan
>
> On Wed, Mar 23, 2011 at 9:01 AM, Eric Ludlam <Eri...@ma...> wrote:
>> Hi,
>>
>>  Can you do:
>>
>> M-x toggle-debug-on-error RET
>>
>> and reproduce the error?  The resulting stack will help identify the culprit.
>>
>> Eric
>>
>> -----Original Message-----
>> From: Alan [mailto:ora...@gm...]
>> Sent: Sunday, March 20, 2011 12:57 AM
>> To: mat...@li...
>> Subject: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)
>>
>> Hi,
>>
>> I'm trying to use just the matlab.el file for editing code. However,
>> if I use any version >= 3.3.0 (corresponding to revision number >=
>> 1.14), I get the following error:
>>
>> File mode specification error: (wrong-type-argument stringp nil)
>>
>> whenever I try to open a .m file in emacs. This happens with emacs
>> versions 21 and 23.
>>
>> Has this happened to anyone before? Know of any fixes?
>>
>> Thanks for your help,
>>
>> Alan
>>
>> ------------------------------------------------------------------------------
>> Colocation vs. Managed Hosting
>> A question and answer guide to determining the best fit
>> for your organization - today and in the future.
>> http://p.sf.net/sfu/internap-sfd2d
>> _______________________________________________
>> Matlab-emacs-discuss mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>>
>
> ------------------------------------------------------------------------------
> Enable your software for Intel(R) Active Management Technology to meet the
> growing manageability and security demands of your customers. Businesses
> are taking advantage of Intel(R) vPro (TM) technology - will your software
> be a part of the solution? Download the Intel(R) Manageability Checker
> today! http://p.sf.net/sfu/intel-dev2devmar
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

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

I was able to reproduce this explicitly when I executed the code by hand, but for some reason it didn't show up when I loaded in matlab files which is how that got checked in today.  I fixed it and checked it in.

I don't know if that fixed your original issue since the error is different, and you didn't have that patch when you had the stringp issue.

Eric

-----Original Message-----
From: Alan [mailto:ora...@gm...] 
Sent: Wednesday, March 23, 2011 2:56 PM
To: mat...@li...
Subject: Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

I just realized I forgot to CC the email list. Here is the reply I
sent to Eric. Sorry to Eric for getting 2 emails!

Thanks for the reply.

Using the latest matlab.el (Revision 1.29), here is the output after
starting 'emacs -nw', then doing M-x toggle-debug-on-error, then C-x
C-f blah.m to create or find a non-existent text file "blah.m":

Debugger entered--Lisp error: (void-variable mlfile)
 (or mlfile "")
 (file-name-directory (or mlfile ""))
 (expand-file-name "toolbox/emacsinit.m" (file-name-directory (or mlfile "")))
 (let ((mlfile ...) (dir ...)) (and mlfile (file-exists-p dir)))
 (defvar matlab-shell-use-emacs-toolbox (let (... ...) (and
mlfile...)) "Add the `matlab-shell' MATLAB toolbox to the MATLAB path
on startup.")
 eval-buffer(#<buffer  *load*> nil "/home/alan/.matlab.el" nil t)  ;
Reading at buffer position 152939
 load-with-code-conversion("/home/alan/.matlab.el"
"/home/alan/.matlab.el" nil t)
 matlab-mode()
 set-auto-mode-0(matlab-mode nil)
 set-auto-mode()
 normal-mode(t)
 after-find-file(t t)
 find-file-noselect-1(#<buffer blah.m> "~/blah.m" nil nil "~/blah.m" nil)
 find-file-noselect("~/blah.m" nil nil t)
 find-file("~/blah.m" t)
 call-interactively(find-file nil nil)


Some further info about my setup: I renamed the file matlab.el to
.matlab.el, and used the following code in my .emacs file:

(autoload 'matlab-mode "~/.matlab" "Enter MATLAB mode." t)
(setq auto-mode-alist (cons '("\\.m\\'" . matlab-mode)
auto-mode-alist))
(autoload 'matlab-shell "~/.matlab" "Interactive MATLAB mode." t)


Any suggestions or hints?

Thanks,
Alan

On Wed, Mar 23, 2011 at 9:01 AM, Eric Ludlam <Eri...@ma...> wrote:
> Hi,
>
>  Can you do:
>
> M-x toggle-debug-on-error RET
>
> and reproduce the error?  The resulting stack will help identify the culprit.
>
> Eric
>
> -----Original Message-----
> From: Alan [mailto:ora...@gm...]
> Sent: Sunday, March 20, 2011 12:57 AM
> To: mat...@li...
> Subject: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)
>
> Hi,
>
> I'm trying to use just the matlab.el file for editing code. However,
> if I use any version >= 3.3.0 (corresponding to revision number >=
> 1.14), I get the following error:
>
> File mode specification error: (wrong-type-argument stringp nil)
>
> whenever I try to open a .m file in emacs. This happens with emacs
> versions 21 and 23.
>
> Has this happened to anyone before? Know of any fixes?
>
> Thanks for your help,
>
> Alan
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

------------------------------------------------------------------------------
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
_______________________________________________
Matlab-emacs-discuss mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

[Alan <ora...@gm...>]

I just realized I forgot to CC the email list. Here is the reply I
sent to Eric. Sorry to Eric for getting 2 emails!

Thanks for the reply.

Using the latest matlab.el (Revision 1.29), here is the output after
starting 'emacs -nw', then doing M-x toggle-debug-on-error, then C-x
C-f blah.m to create or find a non-existent text file "blah.m":

Debugger entered--Lisp error: (void-variable mlfile)
 (or mlfile "")
 (file-name-directory (or mlfile ""))
 (expand-file-name "toolbox/emacsinit.m" (file-name-directory (or mlfile "")))
 (let ((mlfile ...) (dir ...)) (and mlfile (file-exists-p dir)))
 (defvar matlab-shell-use-emacs-toolbox (let (... ...) (and
mlfile...)) "Add the `matlab-shell' MATLAB toolbox to the MATLAB path
on startup.")
 eval-buffer(#<buffer  *load*> nil "/home/alan/.matlab.el" nil t)  ;
Reading at buffer position 152939
 load-with-code-conversion("/home/alan/.matlab.el"
"/home/alan/.matlab.el" nil t)
 matlab-mode()
 set-auto-mode-0(matlab-mode nil)
 set-auto-mode()
 normal-mode(t)
 after-find-file(t t)
 find-file-noselect-1(#<buffer blah.m> "~/blah.m" nil nil "~/blah.m" nil)
 find-file-noselect("~/blah.m" nil nil t)
 find-file("~/blah.m" t)
 call-interactively(find-file nil nil)


Some further info about my setup: I renamed the file matlab.el to
.matlab.el, and used the following code in my .emacs file:

(autoload 'matlab-mode "~/.matlab" "Enter MATLAB mode." t)
(setq auto-mode-alist (cons '("\\.m\\'" . matlab-mode)
auto-mode-alist))
(autoload 'matlab-shell "~/.matlab" "Interactive MATLAB mode." t)


Any suggestions or hints?

Thanks,
Alan

On Wed, Mar 23, 2011 at 9:01 AM, Eric Ludlam <Eri...@ma...> wrote:
> Hi,
>
>  Can you do:
>
> M-x toggle-debug-on-error RET
>
> and reproduce the error?  The resulting stack will help identify the culprit.
>
> Eric
>
> -----Original Message-----
> From: Alan [mailto:ora...@gm...]
> Sent: Sunday, March 20, 2011 12:57 AM
> To: mat...@li...
> Subject: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)
>
> Hi,
>
> I'm trying to use just the matlab.el file for editing code. However,
> if I use any version >= 3.3.0 (corresponding to revision number >=
> 1.14), I get the following error:
>
> File mode specification error: (wrong-type-argument stringp nil)
>
> whenever I try to open a .m file in emacs. This happens with emacs
> versions 21 and 23.
>
> Has this happened to anyone before? Know of any fixes?
>
> Thanks for your help,
>
> Alan
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

Re: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows

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

I checked in the change, plus another posted to this list a couple weeks back about locating a startup script.

Eric

-----Original Message-----
From: rp...@gm... [mailto:rp...@gm...] 
Sent: Wednesday, March 23, 2011 10:14 AM
To: Eric Ludlam
Cc: mat...@li...
Subject: Re: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows

Hi Eric,

the patch fixes it, thank you!

Hans

On Wed, Mar 23, 2011 at 1:59 PM, Eric Ludlam <Eri...@ma...> wrote:
> Hi,
>
>  It looks like the original algorithm was quite simple.  The attached patch will hopefully have the kind of behavior you are looking for.  Let me know how it goes.
>
> Eric
>
> -----Original Message-----
> From: rp...@gm... [mailto:rp...@gm...]
> Sent: Wednesday, March 16, 2011 5:33 AM
> To: mat...@li...
> Subject: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows
>
> Hello everyone,
>
> running matlab-shell 3.3.1 in emacs 23 (ubuntu 10.04), I get the
> following annoying bug:
> Suppose I have to windows open side by side ( source code & matlab-shell ).
> In matlab-shell when I hit Tab to autocomplete for example a function
> name, if this name is not unique, it will show all options in the
> other (source code) window, which is fine. However, if I continue
> typing until the function name or whatever I am autocompleting is
> unique, and hit tab again, the window is closed and now I only have
> one window open, running the matlab-shell. This is very annoying since
> I have split my window again and switch to the source code buffer each
> time I hit tab.
>
> This only happens if the windows are split horizontally (left-right).
>
> I had a look at the function matlab-shell-tab in matlab.el, but I
> don't know enough lisp to see what is happening there. To me it seems
> that the lines (delete-windows-on *Completions*) should only be
> called, if the matlab-shell actually owns these buffers. If not, it
> should just close the *Completions* buffer instead of deleting the
> window
>
> Is this standard behavior or is there something wrong with my emacs?
>
> Thanks
>
> Hans
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

Re: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows

[<rp...@gm...>]

Hi Eric,

the patch fixes it, thank you!

Hans

On Wed, Mar 23, 2011 at 1:59 PM, Eric Ludlam <Eri...@ma...> wrote:
> Hi,
>
>  It looks like the original algorithm was quite simple.  The attached patch will hopefully have the kind of behavior you are looking for.  Let me know how it goes.
>
> Eric
>
> -----Original Message-----
> From: rp...@gm... [mailto:rp...@gm...]
> Sent: Wednesday, March 16, 2011 5:33 AM
> To: mat...@li...
> Subject: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows
>
> Hello everyone,
>
> running matlab-shell 3.3.1 in emacs 23 (ubuntu 10.04), I get the
> following annoying bug:
> Suppose I have to windows open side by side ( source code & matlab-shell ).
> In matlab-shell when I hit Tab to autocomplete for example a function
> name, if this name is not unique, it will show all options in the
> other (source code) window, which is fine. However, if I continue
> typing until the function name or whatever I am autocompleting is
> unique, and hit tab again, the window is closed and now I only have
> one window open, running the matlab-shell. This is very annoying since
> I have split my window again and switch to the source code buffer each
> time I hit tab.
>
> This only happens if the windows are split horizontally (left-right).
>
> I had a look at the function matlab-shell-tab in matlab.el, but I
> don't know enough lisp to see what is happening there. To me it seems
> that the lines (delete-windows-on *Completions*) should only be
> called, if the matlab-shell actually owns these buffers. If not, it
> should just close the *Completions* buffer instead of deleting the
> window
>
> Is this standard behavior or is there something wrong with my emacs?
>
> Thanks
>
> Hans
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>

Re: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

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

Hi,

  Can you do:

M-x toggle-debug-on-error RET

and reproduce the error?  The resulting stack will help identify the culprit.

Eric

-----Original Message-----
From: Alan [mailto:ora...@gm...] 
Sent: Sunday, March 20, 2011 12:57 AM
To: mat...@li...
Subject: [Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

Hi,

I'm trying to use just the matlab.el file for editing code. However,
if I use any version >= 3.3.0 (corresponding to revision number >=
1.14), I get the following error:

File mode specification error: (wrong-type-argument stringp nil)

whenever I try to open a .m file in emacs. This happens with emacs
versions 21 and 23.

Has this happened to anyone before? Know of any fixes?

Thanks for your help,

Alan

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Matlab-emacs-discuss mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows

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

Hi,

  It looks like the original algorithm was quite simple.  The attached patch will hopefully have the kind of behavior you are looking for.  Let me know how it goes.

Eric

-----Original Message-----
From: rp...@gm... [mailto:rp...@gm...] 
Sent: Wednesday, March 16, 2011 5:33 AM
To: mat...@li...
Subject: [Matlab-emacs-discuss] Tab completion in emacs deletes my windows

Hello everyone,

running matlab-shell 3.3.1 in emacs 23 (ubuntu 10.04), I get the
following annoying bug:
Suppose I have to windows open side by side ( source code & matlab-shell ).
In matlab-shell when I hit Tab to autocomplete for example a function
name, if this name is not unique, it will show all options in the
other (source code) window, which is fine. However, if I continue
typing until the function name or whatever I am autocompleting is
unique, and hit tab again, the window is closed and now I only have
one window open, running the matlab-shell. This is very annoying since
I have split my window again and switch to the source code buffer each
time I hit tab.

This only happens if the windows are split horizontally (left-right).

I had a look at the function matlab-shell-tab in matlab.el, but I
don't know enough lisp to see what is happening there. To me it seems
that the lines (delete-windows-on *Completions*) should only be
called, if the matlab-shell actually owns these buffers. If not, it
should just close the *Completions* buffer instead of deleting the
window

Is this standard behavior or is there something wrong with my emacs?

Thanks

Hans

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Matlab-emacs-discuss mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss

Re: [Matlab-emacs-discuss] Problem Building Matlab Emacs

[Aaron G. <aar...@gm...>]

Thanks. I was using CEDET from my ubuntu installation. I was able to use
just matlab.el as you described.

Regards,
Aaron

On Mon, Mar 21, 2011 at 5:08 PM, David Engster <de...@ra...> wrote:

> Aaron Goodman writes:
> > I have been trying to build matlab emacs, but I am running into some
> issues
> > running make. I am using emacs23 and running on ubuntu 10.10
>
> Have you CEDET installed (it probably won't work with the CEDET that
> ships with Emacs)? Look into the INSTALL file for details.
>
> If you're not interested in the Semantic features and just want to use
> matlab.el, just do
>
> emacs --batch -f batch-byte-compile matlab.el
>
> (don't worry about the warnings)
>
> -David
>

Re: [Matlab-emacs-discuss] Problem Building Matlab Emacs

[David E. <de...@ra...>]

Aaron Goodman writes:
> I have been trying to build matlab emacs, but I am running into some issues
> running make. I am using emacs23 and running on ubuntu 10.10

Have you CEDET installed (it probably won't work with the CEDET that
ships with Emacs)? Look into the INSTALL file for details.

If you're not interested in the Semantic features and just want to use
matlab.el, just do

emacs --batch -f batch-byte-compile matlab.el

(don't worry about the warnings)

-David

[Matlab-emacs-discuss] File mode specification error: (wrong-type-argument stringp nil)

[Alan <ora...@gm...>]

Hi,

I'm trying to use just the matlab.el file for editing code. However,
if I use any version >= 3.3.0 (corresponding to revision number >=
1.14), I get the following error:

File mode specification error: (wrong-type-argument stringp nil)

whenever I try to open a .m file in emacs. This happens with emacs
versions 21 and 23.

Has this happened to anyone before? Know of any fixes?

Thanks for your help,

Alan

[Matlab-emacs-discuss] Problem Building Matlab Emacs

[Aaron G. <aar...@gm...>]

Hello,
I have been trying to build matlab emacs, but I am running into some issues
running make. I am using emacs23 and running on ubuntu 10.10

This is the tail end of the make output (though there are many more warnings
preceding that):


semantic-matlab.el:424:20:Warning: attempt to open-code `anonymous lambda'
    with too few arguments
semantic-matlab.el:424:20:Warning: attempt to open-code `anonymous lambda'
    with too few arguments
semantic-matlab.el:424:20:Error: Variable binding depth exceeds
max-specpdl-size

In semanticdb-matlab-cache-files:
semanticdb-matlab.el:248:19:Warning: reference to free variable
    `semantic-matlab-dependency-system-include-path'

In end of data:
semanticdb-matlab.el:383:1:Warning: the function
    `semantic-matlab-find-oldstyle-classes' is not known to be defined.
Wrote /home/aaronjg/src/matlabemacs/matlab-emacs/semanticdb-matlab.elc

In end of data:
cedet-matlab.el:59:1:Warning: the function `srecode-map-update-map' is not
    known to be defined.
Wrote /home/aaronjg/src/matlabemacs/matlab-emacs/cedet-matlab.elc

In company-matlab-shell-tab:
company-matlab-shell.el:30:23:Warning: reference to free variable
    `comint-prompt-regexp'

In company-matlab-shell-grab-symbol:
company-matlab-shell.el:58:26:Warning: reference to free variable
    `comint-prompt-regexp'

In end of data:
company-matlab-shell.el:84:1:Warning: the function `company-begin-backend'
is
    not known to be defined.
Wrote /home/aaronjg/src/matlabemacs/matlab-emacs/company-matlab-shell.elc
make: *** [cedet] Error 1