matlab-emacs-discuss Mailing List for MATLAB in Emacs

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi

Is there a way to change the debug mode so that one can still edit the .m
file even when the program pauses at a break point?
Thanks!

Jiaen

The commit below fixes a number of issues with MATLAB code sections, one of
which is adding default key bindings, C-c C-<KEY> and C-c M-<KEY>, which
means code sections key bindings work on systems without the super key. The
super key bindings can be added by customizing
matlab-sections-use-super-key. This commit also adds a "MATLAB -> Code
Sections" menu and selecting the help from that menu will let you customize
matlab-sections-use-super-key

https://github.com/mathworks/Emacs-MATLAB-Mode/commit/e75ebf5a88b02833d700bcf9ee4419c5888caf12

John

Please consider the following trivial .m file called example.m
%% 
fprintf('* Paso 2: Calculamos la región de aceptación $R_A$.\n\n')

What works

    1. I open matlab indenpendent from emacs, and fire this command in
       the command line. Everything works

    2. I open emacs start matlab,  matlab-shell the command
       example.m, everything works

    3. I run in the shell fprintf('* Paso 2: Calculamos la región de
       aceptación $R_A$.\n\n')
       the non ASCII symbols are not displayed!

    4. I run in the file matlab-shell-run-code-section
       and again, the ASCII symbols are not displayed.

Shall I open an issue?

Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

It's probably fine to not print the version number when matlab-shell starts.  I don't think any other shell fcns print their version number.  A holdover from a different age.

Eric

-----Original Message-----
From: Uwe Brauer <ou...@ma...> 
Sent: Saturday, December 7, 2024 2:40 AM
To: Eric Ludlam <el...@ma...>
Cc: Uwe Brauer <ou...@ma...>; mat...@li...; John Ciolfi <ci...@ma...>
Subject: Re: matlab-version/matlab-show-version

>>> "EL" == Eric Ludlam <el...@ma...> writes:

>> From: Uwe Brauer <ou...@ma...> 
>>>>> "EL" == Eric Ludlam <el...@ma...> writes:

>>> The command matlab-show-version was always there since before I
>>> adopted matlab-mode. I'm not attached to it and would not mind if it
>>> were removed.

>> According to git blame or mercurial annotate, you are the author 😉
>> (however this functionality is not very reliable, since any chance in
>> the indent etc, is registered.

> Makes sense - Matt emailed me the file, and I put it into version control.  I think it was RCS at the time. 😊

I had to revert to commit b2baf6b106587480 causes problems with
matlab-shell.

I now understand why this function was added, it displays the
matlab-mode version when the shell is called.

However there is a byte compiler warning with this function namely 
In matlab-show-version:
matlab.el:1473:38: Warning: reference to free variable ‘matlab-mode-version’

Which was pointed out to me by the ELPA and MELPA maintainers.

What shall we do, any thought?

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

>>> "UB" == Uwe Brauer <ou...@ma...> writes:

> Hi 

> currently make lisp works but 
> make test fails with the error 

Please ignore this message. I caused this problem by playing around with too many different ways to define 

 matlab-mode-version 

> ebugger entered--Lisp error: (void-variable matlab-mode-version)
>   (string= package-version matlab-mode-version)
>   (not (string= package-version matlab-mode-version))
>   (if (not (string= package-version matlab-mode-version)) (progn (user-error "Version from matlab-mode.el \";; Version: %s\" != ma..." package-version matlab-mode-version)))
>   (let ((package-version (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents "../matlab-mode.el") (if ... ...) (match-string 1)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer))))))) (if (not (string= package-version matlab-mode-version)) (progn (user-error "Version from matlab-mode.el \";; Version: %s\" != ma..." package-version matlab-mode-version))))
>   metest-check-version()
>   metest-all-syntax-tests()
>   command-line-1(("--eval" "(setq debug-on-error t)" "-l" "metest.el" "-e" "metest-all-syntax-tests"))
>   command-line()
>   normal-top-level()

> make[1]: *** [Makefile:35: modetests] Error 255
> make[1]: Leaving directory '/home/oub/ALLES/src/src-emacs-pkg/Matlab/Github/SSH/emacs-matlab-hg/tests'
> make: *** [Makefile:86: .tests.tstamp] Error 2

> The error was caused by commit 864ff8a925a28f (from the fill-fix branch
> which I merged into default and did not notice the problem)

> The problem is this change in metest.el

> +(defun metest-check-version ()
> +  "Validate matlab-mode version numbers are consistent."
> +  (let ((package-version (with-temp-buffer
> +                           (insert-file-contents "../matlab-mode.el")
> +                           (when (not (re-search-forward
> +                                       "^;; Version: \\([0-9]+\\.[0-9]+\\)[ \t]*$" nil t))
> +                             (user-error "Failed to find version in ../matlab-mode.el"))
> +                           (match-string 1))))
> +    (when (not (string= package-version matlab-mode-version))
> +      (user-error "Version from matlab-mode.el \";; Version: %s\" != matlab-mode-version %s"
> +                  package-version matlab-mode-version))))
> +
> +

> John you introduced this.

> I think it is time to discuss several things

>     1. Should we keep the function matlab-show-version (for matlab-shell)

>     2. Shall we have the defconst 

> (defconst matlab-mode-version "6.2"
>   "Current version of MATLAB(R) mode.")

>     Either in matlab.el or matlab-mode.el?

> I had to revert to commit 

> B2baf6b106587480 to reintroduce the matlab-mode-version, otherwise make
> lisp fails which is a show-stopper for ELPA and MELPA.

> I hesitate to revert metest.el before we discuss its implication

> I think we should settle this as soon as possible. I will put this as an
> issue in github as well

> Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

Hi 

currently make lisp works but 
make test fails with the error 
--8<---------------cut here---------------start------------->8---
ebugger entered--Lisp error: (void-variable matlab-mode-version)
  (string= package-version matlab-mode-version)
  (not (string= package-version matlab-mode-version))
  (if (not (string= package-version matlab-mode-version)) (progn (user-error "Version from matlab-mode.el \";; Version: %s\" != ma..." package-version matlab-mode-version)))
  (let ((package-version (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn (insert-file-contents "../matlab-mode.el") (if ... ...) (match-string 1)) (and (buffer-name temp-buffer) (kill-buffer temp-buffer))))))) (if (not (string= package-version matlab-mode-version)) (progn (user-error "Version from matlab-mode.el \";; Version: %s\" != ma..." package-version matlab-mode-version))))
  metest-check-version()
  metest-all-syntax-tests()
  command-line-1(("--eval" "(setq debug-on-error t)" "-l" "metest.el" "-e" "metest-all-syntax-tests"))
  command-line()
  normal-top-level()

make[1]: *** [Makefile:35: modetests] Error 255
make[1]: Leaving directory '/home/oub/ALLES/src/src-emacs-pkg/Matlab/Github/SSH/emacs-matlab-hg/tests'
make: *** [Makefile:86: .tests.tstamp] Error 2
--8<---------------cut here---------------end--------------->8---

The error was caused by commit 864ff8a925a28f (from the fill-fix branch
which I merged into default and did not notice the problem)

The problem is this change in metest.el

--8<---------------cut here---------------start------------->8---

+(defun metest-check-version ()
+  "Validate matlab-mode version numbers are consistent."
+  (let ((package-version (with-temp-buffer
+                           (insert-file-contents "../matlab-mode.el")
+                           (when (not (re-search-forward
+                                       "^;; Version: \\([0-9]+\\.[0-9]+\\)[ \t]*$" nil t))
+                             (user-error "Failed to find version in ../matlab-mode.el"))
+                           (match-string 1))))
+    (when (not (string= package-version matlab-mode-version))
+      (user-error "Version from matlab-mode.el \";; Version: %s\" != matlab-mode-version %s"
+                  package-version matlab-mode-version))))
+
+

--8<---------------cut here---------------end--------------->8---

John you introduced this.

I think it is time to discuss several things

    1. Should we keep the function matlab-show-version (for matlab-shell)

    2. Shall we have the defconst 

(defconst matlab-mode-version "6.2"
  "Current version of MATLAB(R) mode.")

    Either in matlab.el or matlab-mode.el?

I had to revert to commit 

B2baf6b106587480 to reintroduce the matlab-mode-version, otherwise make
lisp fails which is a show-stopper for ELPA and MELPA.

I hesitate to revert metest.el before we discuss its implication

I think we should settle this as soon as possible. I will put this as an
issue in github as well

Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

>>> "EL" == Eric Ludlam <el...@ma...> writes:

>> From: Uwe Brauer <ou...@ma...> 
>>>>> "EL" == Eric Ludlam <el...@ma...> writes:

>>> The command matlab-show-version was always there since before I
>>> adopted matlab-mode. I'm not attached to it and would not mind if it
>>> were removed.

>> According to git blame or mercurial annotate, you are the author 😉
>> (however this functionality is not very reliable, since any chance in
>> the indent etc, is registered.

> Makes sense - Matt emailed me the file, and I put it into version control.  I think it was RCS at the time. 😊

I had to revert to commit b2baf6b106587480 causes problems with
matlab-shell.

I now understand why this function was added, it displays the
matlab-mode version when the shell is called.

However there is a byte compiler warning with this function namely 
In matlab-show-version:
matlab.el:1473:38: Warning: reference to free variable ‘matlab-mode-version’

Which was pointed out to me by the ELPA and MELPA maintainers.

What shall we do, any thought?

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

> Makes sense - Matt emailed me the file, and I put it into version control.  I think it was RCS at the time. 😊

I just checked, matlab-shell uses 
matlab-show-version

So the question is do we want to keep it, maybe people want to see the matlab-show-version when calling matlab-shell?

I will move the function  back for the moment till the issue is settled because otherwise the test fails and matlab-mode cannot be compiled

> Eric

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

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

>>>> "EL" == Eric Ludlam <el...@ma...> writes:

>> The command matlab-show-version was always there since before I
>> adopted matlab-mode. I'm not attached to it and would not mind if it
>> were removed.

> According to git blame or mercurial annotate, you are the author 😉
> (however this functionality is not very reliable, since any chance in
> the indent etc, is registered.

Makes sense - Matt emailed me the file, and I put it into version control.  I think it was RCS at the time. 😊

Eric

>>> "EL" == Eric Ludlam <el...@ma...> writes:

> The command matlab-show-version was always there since before I
> adopted matlab-mode. I'm not attached to it and would not mind if it
> were removed.

According to git blame or mercurial annotate, you are the author 😉
(however this functionality is not very reliable, since any chance in
the indent etc, is registered.

Ok I remove it then

> For matlab-version, do you mean matlab-mode-version? As for why
> defconst, seems reasonable to me since it's a constant. 😊

Yep, matlab-mode-version.

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

The command matlab-show-version was always there since before I adopted matlab-mode.  I'm not attached to it and would not mind if it were removed.

For matlab-version, do you mean matlab-mode-version?  As for why defconst, seems reasonable to me since it's a constant. 😊

Eric

-----Original Message-----
From: Uwe Brauer <ou...@ma...> 
Sent: Thursday, December 5, 2024 12:54 PM
To: mat...@li...
Cc: Eric Ludlam <el...@ma...>; John Ciolfi <ci...@ma...>
Subject: matlab-version/matlab-show-version

Hi

I am currently dealing to get  matlab-mode into ELPA. I will also open an issue in github (not sure what is better for most of you

The ELPA maintainer, told me 

    1. Why do we have still the function matlab-show-version

    2. And matlab-version as a defconst

    3. And where to put the defconst in matlab.el or in matlab-mode.el The MELPA maintainer recommended the introduction of this file. 

I will also write him

Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

Hi

I am currently dealing to get  matlab-mode into ELPA. I will also open an issue in github (not sure what is better for most of you

The ELPA maintainer, told me 

    1. Why do we have still the function matlab-show-version

    2. And matlab-version as a defconst

    3. And where to put the defconst in matlab.el or in matlab-mode.el The MELPA maintainer recommended the introduction of this file. 

I will also write him

Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

I found the github issue about matlab-sections and the highlighting issue,
and added a patch there that should both resolve the issue, and make it
easier to add new features unique to different types of MATLAB files.

Eric

On Wed, Nov 20, 2024 at 3:10 PM Uwe Brauer <ou...@ma...> wrote:

> >>> "EL" == Eric Ludlam <eri...@gm...> writes:
>
> > Thanks for the feedback.
> > I was proposing adding a 2nd set of bindings.  For folks with super-key,
> > the current bindings will be faster.  More obscure bindings won't get in
> > their way.
>
> > As for C-c %  vs C-c C-<key> - the Elisp manual is pretty specific saying
> > that C-<punctuation> is reserved for minor modes (excluding ; : { and }
> ).
> >  I picked % out of a hat since it is a comment character.
>
> > As for the bolding effect, that is an overlay in matlab-sections, and if
> > you turn off sections mode, then it goes away.  Sections mode just
> happens
> > to have also adopted the face used for %% comments.  It would be easy to
> > change the defface in sections to inherit from `font-lock-comment-face'
> and
> > fix general font locking.  I lost track of where the actual font lock
> usage
> > of it is, but the defface should be near the font-lock regexps.
>
> Well I just started to use the new section features on a more regular
> base, and I still am not sure whether I like is or prefer to tweak a bit
> the setting.
>
> > As for auto-choosing when to enable detection of sections to avoid
> bolding
> > in functions 'matlab-guess-script-type' already detects the basics of
> what
> > is needed.  It could just not add its post-command-hook if not in a
> > script.  Sections would then also need to watch when this value changes
> and
> > reset itself - typically when one goes from an empty file to one with a
> > function decl in it.
>
> > I'll go look in that other thread too.  Thanks for pointing it out.  I
> > hadn't realized how much I missed b/c the emails are getting binned in a
> > weird place for me when I rearranged my mailing list subscriptions.
>
> Well now, we mostly use issues, not that I am a huge fan, but I can see its
> benefits, and I also managed to configure magit/forge so that I can
> access them from within Emacs which is a big plus.
>
> Uwe
> --
> I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
> I strongly condemn Putin's war of aggression against Ukraine.
> I support to deliver weapons to Ukraine's military.
> I support the EU and NATO membership of Ukraine.
>
>

I just want to inform everyone, that soon matlab-mode will appear in ELPA. The main difference is that in ELPA only a new version is released if we change explicitely the version number, while MELPA release a new version for every push.

We have then also to modify the file CONTRIBUTING.org since we need all contributors to sign the FSF papers.

Any ideas o thoughts?

Uwe Brauer
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

OK, foound information in the github site on the org features. Very cool!
Thanks,
Vasco

On Sat, Nov 23, 2024 at 12:14 PM <
mat...@li...> wrote:

> Send Matlab-emacs-discuss mailing list submissions to
>         mat...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
> or, via email, send a message with subject or body 'help' to
>         mat...@li...
>
> You can reach the person managing the list at
>         mat...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Matlab-emacs-discuss digest..."
>
>
> Today's Topics:
>
>    1. Re: having emacs-matlab in ELPA, finally. FSF paper signed
>       (Uwe Brauer)
>    2. Re: Matlab-emacs-discuss Digest, Vol 122, Issue 8 (Vasco C?rdia)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 23 Nov 2024 14:19:30 +0100
> From: Uwe Brauer <ou...@ma...>
> To: Philip Kaludercic <ph...@po...>
> Cc: Uwe Brauer <ou...@ma...>, Andrea Corallo <aco...@gn...>,
>         <ema...@gn...>, Matlab-emacs-discuss
>         <mat...@li...>
> Subject: Re: [Matlab-emacs-discuss] having emacs-matlab in ELPA,
>         finally. FSF paper signed
> Message-ID: <874...@ma...>
> Content-Type: text/plain; charset="us-ascii"
>
>
> > Uwe Brauer <ou...@ma...> writes:
>
> > You don't have to do anything*, I just have to add a package
> > specification (similar to the "recipe file" for MELPA) to elpa.git.
>
> > * As soon as it works.  The main issues right now, are as you noticed
> >   that ELPA doesn't release a new tarball for every commit, but just
> >   when a new version is released.  We track this by checking for commits
> >   that bump the "Version" header in the main file (in your case
> >   matlab.el).  You currently don't have any version number, so the build
> >   fails.  I would suggest applying a change like this, if it doesn't
> >   break any assumptions you have regarding the minimal Emacs version:
>
> > diff --git a/matlab.el b/matlab.el
> > index 8ca0ee24a2..b82229a672 100644
> > --- a/matlab.el
> > +++ b/matlab.el
> > @@ -5,11 +5,7 @@
> >  ;; Maintainer: Eric M. Ludlam <el...@ma...>
> >  ;; Created: 04 Jan 91
> >  ;; Keywords: MATLAB(R)
> > -;; Version:
> > -
> > -(defconst matlab-mode-version "5.0"
> > -  "Current version of MATLAB(R) mode.")
> > -
> > +;; Version: 5.0
> >  ;;
> >  ;; Copyright (C) 1997-2022 Eric M. Ludlam
> >  ;; Copyright (C) 1991-1997 Matthew R. Wette
> > @@ -50,6 +46,10 @@
>
> >  ;;; Code:
>
> > +(defconst matlab-mode-version (package-get-version)
> > +  "Current version of MATLAB(R) mode.")
> > +
> > +
> >  (require 'matlab-compat)
> >  (require 'matlab-syntax)
> >  (require 'matlab-scan)
>
> A couple of remarks,
>
>     1. this diff seems against an older matlab-mode version (may the one
>        in sourceforge), the latest github version is 6.2
>        https://github.com/mathworks/Emacs-MATLAB-Mode.git
>
>     2. Jonas Bernoulli one of the MELPA maintainers, recommended (but
>        did not demand) to add file called matlab-mode.el which is
>        basically a dummy file but also contains the current version
>
>
> >   The other issue is that ELPA checks the copyright string and wants to
> >   see that all packages in GNU ELPA have their copyright assigned to the
> >   FSF.
>
> There is an automated process for checking this. If I had known, it
> would have saved my quite a bit of time and work. I eyeballed the logs
> and if there was an unknown author I checked the diff, and if necessary
> contacted him.
>
> >   If you can fix these two things, then everything should go through.
> >   You can then decide to filter out files out of the final tarball by
> >   adding an .elpaignore file that lists what files to exclude.
>
>
>     1. I will add an elpaignore file, which is urgent,
>
>     2. And concerning the version number, what shall I do, your proposal
>        or Stefan's?
>
> For the moment being I would like to keep the MELPA version as well till
> I know ELPA works
>
> Uwe
>
> --
> I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
> I strongly condemn Putin's war of aggression against Ukraine.
> I support to deliver weapons to Ukraine's military.
> I support the EU and NATO membership of Ukraine.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 5684 bytes
> Desc: not available
>
> ------------------------------
>
> Message: 2
> Date: Sat, 23 Nov 2024 12:13:21 -0800
> From: Vasco C?rdia <vc...@gm...>
> To: mat...@li...
> Subject: Re: [Matlab-emacs-discuss] Matlab-emacs-discuss Digest, Vol
>         122, Issue 8
> Message-ID:
>         <CAC_+eD+hrwR3wf-KLAMV1xMGz4OqfCk8x2yb7fMouqpa==
> t1...@ma...>
> Content-Type: text/plain; charset="utf-8"
>
> What kind of org integration does matlab-mode offer?
>
> I do use org, so I'd like to know how much I can leverage any features
> available.
>
> Thanks,
> Vasco
>
> On Sat, Nov 23, 2024 at 4:27?AM <
> mat...@li...> wrote:
>
> > Send Matlab-emacs-discuss mailing list submissions to
> >         mat...@li...
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
> > or, via email, send a message with subject or body 'help' to
> >         mat...@li...
> >
> > You can reach the person managing the list at
> >         mat...@li...
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Matlab-emacs-discuss digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: [Matlab+org (use the python eninge or not)] (Uwe Brauer)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Fri, 22 Nov 2024 16:53:18 +0100
> > From: Uwe Brauer <ou...@ma...>
> > To: martinoidar <mar...@gm...>
> > Cc: Uwe Brauer <ou...@ma...>, Matlab-emacs-discuss
> >         <mat...@li...>
> > Subject: Re: [Matlab-emacs-discuss] [Matlab+org (use the python eninge
> >         or not)]
> > Message-ID: <87a...@ma...>
> > Content-Type: text/plain; charset="us-ascii"
> >
> >
> > > On 25.04.2024 21:55, martinoidar wrote:
> >
> > Hi
> > > Update:
> >
> > > I've just noticed that not everything is properly rendered in markdown
> > > form.
> >
> > I just want to point out that we merged successfully our org-mode branch
> > into the main, the default branch, and now the native org supports works
> > flawlessly and does not require the python engine anymore. You can
> > access the newest version either via MELPA or directly from
> > https://github.com/mathworks/Emacs-MATLAB-Mode.git
> >
> >
> > Uwe Brauer
> > --
> > I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
> > I strongly condemn Putin's war of aggression against Ukraine.
> > I support to deliver weapons to Ukraine's military.
> > I support the EU and NATO membership of Ukraine.
> >
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: smime.p7s
> > Type: application/pkcs7-signature
> > Size: 5684 bytes
> > Desc: not available
> >
> > ------------------------------
> >
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > Matlab-emacs-discuss mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
> >
> >
> > ------------------------------
> >
> > End of Matlab-emacs-discuss Digest, Vol 122, Issue 8
> > ****************************************************
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>
>
> ------------------------------
>
> End of Matlab-emacs-discuss Digest, Vol 122, Issue 9
> ****************************************************
>

What kind of org integration does matlab-mode offer?

I do use org, so I'd like to know how much I can leverage any features
available.

Thanks,
Vasco

On Sat, Nov 23, 2024 at 4:27 AM <
mat...@li...> wrote:

> Send Matlab-emacs-discuss mailing list submissions to
>         mat...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
> or, via email, send a message with subject or body 'help' to
>         mat...@li...
>
> You can reach the person managing the list at
>         mat...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Matlab-emacs-discuss digest..."
>
>
> Today's Topics:
>
>    1. Re: [Matlab+org (use the python eninge or not)] (Uwe Brauer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 22 Nov 2024 16:53:18 +0100
> From: Uwe Brauer <ou...@ma...>
> To: martinoidar <mar...@gm...>
> Cc: Uwe Brauer <ou...@ma...>, Matlab-emacs-discuss
>         <mat...@li...>
> Subject: Re: [Matlab-emacs-discuss] [Matlab+org (use the python eninge
>         or not)]
> Message-ID: <87a...@ma...>
> Content-Type: text/plain; charset="us-ascii"
>
>
> > On 25.04.2024 21:55, martinoidar wrote:
>
> Hi
> > Update:
>
> > I've just noticed that not everything is properly rendered in markdown
> > form.
>
> I just want to point out that we merged successfully our org-mode branch
> into the main, the default branch, and now the native org supports works
> flawlessly and does not require the python engine anymore. You can
> access the newest version either via MELPA or directly from
> https://github.com/mathworks/Emacs-MATLAB-Mode.git
>
>
> Uwe Brauer
> --
> I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
> I strongly condemn Putin's war of aggression against Ukraine.
> I support to deliver weapons to Ukraine's military.
> I support the EU and NATO membership of Ukraine.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: smime.p7s
> Type: application/pkcs7-signature
> Size: 5684 bytes
> Desc: not available
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Matlab-emacs-discuss mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matlab-emacs-discuss
>
>
> ------------------------------
>
> End of Matlab-emacs-discuss Digest, Vol 122, Issue 8
> ****************************************************
>

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

> You don't have to do anything*, I just have to add a package
> specification (similar to the "recipe file" for MELPA) to elpa.git.

> * As soon as it works.  The main issues right now, are as you noticed
>   that ELPA doesn't release a new tarball for every commit, but just
>   when a new version is released.  We track this by checking for commits
>   that bump the "Version" header in the main file (in your case
>   matlab.el).  You currently don't have any version number, so the build
>   fails.  I would suggest applying a change like this, if it doesn't
>   break any assumptions you have regarding the minimal Emacs version:

> diff --git a/matlab.el b/matlab.el
> index 8ca0ee24a2..b82229a672 100644
> --- a/matlab.el
> +++ b/matlab.el
> @@ -5,11 +5,7 @@
>  ;; Maintainer: Eric M. Ludlam <el...@ma...>
>  ;; Created: 04 Jan 91
>  ;; Keywords: MATLAB(R)
> -;; Version:
> -
> -(defconst matlab-mode-version "5.0"
> -  "Current version of MATLAB(R) mode.")
> -
> +;; Version: 5.0
>  ;;
>  ;; Copyright (C) 1997-2022 Eric M. Ludlam
>  ;; Copyright (C) 1991-1997 Matthew R. Wette
> @@ -50,6 +46,10 @@

>  ;;; Code:

> +(defconst matlab-mode-version (package-get-version)
> +  "Current version of MATLAB(R) mode.")
> +
> +
>  (require 'matlab-compat)
>  (require 'matlab-syntax)
>  (require 'matlab-scan)

A couple of remarks, 

    1. this diff seems against an older matlab-mode version (may the one
       in sourceforge), the latest github version is 6.2
       https://github.com/mathworks/Emacs-MATLAB-Mode.git

    2. Jonas Bernoulli one of the MELPA maintainers, recommended (but
       did not demand) to add file called matlab-mode.el which is
       basically a dummy file but also contains the current version 

>   The other issue is that ELPA checks the copyright string and wants to
>   see that all packages in GNU ELPA have their copyright assigned to the
>   FSF.

There is an automated process for checking this. If I had known, it
would have saved my quite a bit of time and work. I eyeballed the logs
and if there was an unknown author I checked the diff, and if necessary
contacted him. 

>   If you can fix these two things, then everything should go through.
>   You can then decide to filter out files out of the final tarball by
>   adding an .elpaignore file that lists what files to exclude.

    1. I will add an elpaignore file, which is urgent,

    2. And concerning the version number, what shall I do, your proposal
       or Stefan's?

For the moment being I would like to keep the MELPA version as well till
I know ELPA works

Uwe 

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

> On 25.04.2024 21:55, martinoidar wrote:

Hi 
> Update:

> I've just noticed that not everything is properly rendered in markdown
> form.

I just want to point out that we merged successfully our org-mode branch
into the main, the default branch, and now the native org supports works
flawlessly and does not require the python engine anymore. You can
access the newest version either via MELPA or directly from
https://github.com/mathworks/Emacs-MATLAB-Mode.git

Uwe Brauer 
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

>>> "JC" == John Ciolfi <ci...@ma...> writes:

> --_000_mn2pr05mb6766aec9347374bef65023cbd1212mn2pr05mb6766namp_
> Content-type: text/plain; charset="windows-1252"
> Content-transfer-encoding: quoted-printable

> Hi

> I think we could keep the current settings for those that don't have issues=
>  with the super key. We could also have the C-c C-<ITEM> key binding witch =
> is similar to the current settings.

> I'm not sure which is better using C-c C-<ITEM> or C-% <ITEM>? Both seem re=
> asonable to me.

> We should probably have the super key bindings be "2nd" because it doesn't =
> work in several cases. Windows can loose access to the super key, in cases =
> it doesn't exist on Linux, and Mac doesn't have a super key.

Well, indeed Mac does have a super key, but emacs compiled for Mac has. 😉
That is you can configure your emacs so that there is a super key.

If needed I can provide the details (I also have a Mac Air, that I use
for teaching).

> Thanks

> ________________________________
> From: Uwe Brauer
> Sent: Wednesday, November 20, 2024 12:05 PM
> To: John Ciolfi via Matlab-emacs-discuss
> Cc: Eric Ludlam; John Ciolfi
> Subject: Re: [Matlab-emacs-discuss] matlab-sections.el

>>> "JCvM" =3D=3D John Ciolfi via Matlab-emacs-discuss <matlab-emacs-discus=
> s...@li...> writes:

>> Yes, it's a good feature when working with scripts.
>> The key binding is an issue I see too, though when using VNC.
>> Sometimes the super key isn't passed through. It's also common for the
>> windows super key to not work on Windows, see
>> https://answers.microsoft.com/en-us/windows/forum/all/windows-key-not-wor=
> king/0c796f79-0aa8-466e-ab44-802005d1791b
>> which gives 8 methods for fixing that. I've hit this in the past.

>> What about:

>> (define-key map (kbd "C-c C-<down>") #'matlab-sections-forward-sectio=
> n)
>> (define-key map (kbd "C-C C-<up>") #'matlab-sections-backward-section=
> )
>> (define-key map (kbd "C-C C-<left>") #'matlab-sections-beginning-of-s=
> ection)
>> (define-key map (kbd "C-C C-<right>") #'matlab-sections-end-of-sectio=
> n)
>> (define-key map (kbd "C-c M-<up>") #'matlab-sections-move-section-up)
>> (define-key map (kbd "C-c M-<down>") #'matlab-sections-move-section-d=
> own)
>> (define-key map (kbd "C-c M-<return>") #'matlab-sections-run-till-poi=
> nt)
>> (define-key map (kbd "C-c C-SPC") #'matlab-sections-mark-section)

> Do you mean: in addition to the current keybinding setting or replacing
> the  current keybinding?

> If the current keybinding is problematic for Linux users, can't we
> distinguish between the two or say  OS.

>     1. MacOS: darwin

>     2. Linux: gnu/linux

>     3. MS, windows-nt
> Like

> (if (eq system-type 'darwin)
>   ; something for OS X if true
>   ; optional something if not
> )

-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

>>> "EL" == Eric Ludlam <eri...@gm...> writes:

> Thanks for the feedback.
> I was proposing adding a 2nd set of bindings.  For folks with super-key,
> the current bindings will be faster.  More obscure bindings won't get in
> their way.

> As for C-c %  vs C-c C-<key> - the Elisp manual is pretty specific saying
> that C-<punctuation> is reserved for minor modes (excluding ; : { and } ).
>  I picked % out of a hat since it is a comment character.

> As for the bolding effect, that is an overlay in matlab-sections, and if
> you turn off sections mode, then it goes away.  Sections mode just happens
> to have also adopted the face used for %% comments.  It would be easy to
> change the defface in sections to inherit from `font-lock-comment-face' and
> fix general font locking.  I lost track of where the actual font lock usage
> of it is, but the defface should be near the font-lock regexps.

Well I just started to use the new section features on a more regular
base, and I still am not sure whether I like is or prefer to tweak a bit
the setting.

> As for auto-choosing when to enable detection of sections to avoid bolding
> in functions 'matlab-guess-script-type' already detects the basics of what
> is needed.  It could just not add its post-command-hook if not in a
> script.  Sections would then also need to watch when this value changes and
> reset itself - typically when one goes from an empty file to one with a
> function decl in it.

> I'll go look in that other thread too.  Thanks for pointing it out.  I
> hadn't realized how much I missed b/c the emails are getting binned in a
> weird place for me when I rearranged my mailing list subscriptions.

Well now, we mostly use issues, not that I am a huge fan, but I can see its
benefits, and I also managed to configure magit/forge so that I can
access them from within Emacs which is a big plus.

Uwe 
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

Thanks for the feedback.

I was proposing adding a 2nd set of bindings.  For folks with super-key,
the current bindings will be faster.  More obscure bindings won't get in
their way.

As for C-c %  vs C-c C-<key> - the Elisp manual is pretty specific saying
that C-<punctuation> is reserved for minor modes (excluding ; : { and } ).
 I picked % out of a hat since it is a comment character.

As for the bolding effect, that is an overlay in matlab-sections, and if
you turn off sections mode, then it goes away.  Sections mode just happens
to have also adopted the face used for %% comments.  It would be easy to
change the defface in sections to inherit from `font-lock-comment-face' and
fix general font locking.  I lost track of where the actual font lock usage
of it is, but the defface should be near the font-lock regexps.

As for auto-choosing when to enable detection of sections to avoid bolding
in functions 'matlab-guess-script-type' already detects the basics of what
is needed.  It could just not add its post-command-hook if not in a
script.  Sections would then also need to watch when this value changes and
reset itself - typically when one goes from an empty file to one with a
function decl in it.

I'll go look in that other thread too.  Thanks for pointing it out.  I
hadn't realized how much I missed b/c the emails are getting binned in a
weird place for me when I rearranged my mailing list subscriptions.

Eric

On Wed, Nov 20, 2024 at 2:28 PM John Ciolfi <ci...@ma...> wrote:

> Hi
>
> I think we could keep the current settings for those that don't have
> issues with the super key. We could also have the C-c C-<ITEM> key binding
> witch is similar to the current settings.
>
> I'm not sure which is better using C-c C-<ITEM> or C-% <ITEM>? Both seem
> reasonable to me.
>
> We should probably have the super key bindings be "2nd" because it doesn't
> work in several cases. Windows can loose access to the super key, in cases
> it doesn't exist on Linux, and Mac doesn't have a super key.
>
> Thanks
>
>
> ------------------------------
> *From:* Uwe Brauer
> *Sent:* Wednesday, November 20, 2024 12:05 PM
> *To:* John Ciolfi via Matlab-emacs-discuss
> *Cc:* Eric Ludlam; John Ciolfi
> *Subject:* Re: [Matlab-emacs-discuss] matlab-sections.el
>
> >>> "JCvM" == John Ciolfi via Matlab-emacs-discuss <
> mat...@li...> writes:
>
> > Yes, it's a good feature when working with scripts.
> > The key binding is an issue I see too, though when using VNC.
> > Sometimes the super key isn't passed through. It's also common for the
> > windows super key to not work on Windows, see
> >
> https://answers.microsoft.com/en-us/windows/forum/all/windows-key-not-working/0c796f79-0aa8-466e-ab44-802005d1791b
> > which gives 8 methods for fixing that. I've hit this in the past.
>
> > What about:
>
> >     (define-key map (kbd "C-c C-<down>")
> #'matlab-sections-forward-section)
> >     (define-key map (kbd "C-C C-<up>")
> #'matlab-sections-backward-section)
> >     (define-key map (kbd "C-C C-<left>")
> #'matlab-sections-beginning-of-section)
> >     (define-key map (kbd "C-C C-<right>")
> #'matlab-sections-end-of-section)
> >     (define-key map (kbd "C-c M-<up>") #'matlab-sections-move-section-up)
> >     (define-key map (kbd "C-c M-<down>")
> #'matlab-sections-move-section-down)
> >     (define-key map (kbd "C-c M-<return>")
> #'matlab-sections-run-till-point)
> >     (define-key map (kbd "C-c C-SPC") #'matlab-sections-mark-section)
>
>
> Do you mean: in addition to the current keybinding setting or replacing
> the  current keybinding?
>
>
> If the current keybinding is problematic for Linux users, can't we
> distinguish between the two or say  OS.
>
>
>     1. MacOS: darwin
>
>     2. Linux: gnu/linux
>
>     3. MS, windows-nt
> Like
>
> (if (eq system-type 'darwin)
>   ; something for OS X if true
>   ; optional something if not
> )
> --
> I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
> I strongly condemn Putin's war of aggression against Ukraine.
> I support to deliver weapons to Ukraine's military.
> I support the EU and NATO membership of Ukraine.
>
>

Hi

I think we could keep the current settings for those that don't have issues with the super key. We could also have the C-c C-<ITEM> key binding witch is similar to the current settings.

I'm not sure which is better using C-c C-<ITEM> or C-% <ITEM>? Both seem reasonable to me.

We should probably have the super key bindings be "2nd" because it doesn't work in several cases. Windows can loose access to the super key, in cases it doesn't exist on Linux, and Mac doesn't have a super key.

Thanks

________________________________
From: Uwe Brauer
Sent: Wednesday, November 20, 2024 12:05 PM
To: John Ciolfi via Matlab-emacs-discuss
Cc: Eric Ludlam; John Ciolfi
Subject: Re: [Matlab-emacs-discuss] matlab-sections.el

>>> "JCvM" == John Ciolfi via Matlab-emacs-discuss <mat...@li...> writes:

> Yes, it's a good feature when working with scripts.
> The key binding is an issue I see too, though when using VNC.
> Sometimes the super key isn't passed through. It's also common for the
> windows super key to not work on Windows, see
> https://answers.microsoft.com/en-us/windows/forum/all/windows-key-not-working/0c796f79-0aa8-466e-ab44-802005d1791b
> which gives 8 methods for fixing that. I've hit this in the past.

> What about:

>     (define-key map (kbd "C-c C-<down>") #'matlab-sections-forward-section)
>     (define-key map (kbd "C-C C-<up>") #'matlab-sections-backward-section)
>     (define-key map (kbd "C-C C-<left>") #'matlab-sections-beginning-of-section)
>     (define-key map (kbd "C-C C-<right>") #'matlab-sections-end-of-section)
>     (define-key map (kbd "C-c M-<up>") #'matlab-sections-move-section-up)
>     (define-key map (kbd "C-c M-<down>") #'matlab-sections-move-section-down)
>     (define-key map (kbd "C-c M-<return>") #'matlab-sections-run-till-point)
>     (define-key map (kbd "C-c C-SPC") #'matlab-sections-mark-section)

Do you mean: in addition to the current keybinding setting or replacing
the  current keybinding?

If the current keybinding is problematic for Linux users, can't we
distinguish between the two or say  OS.

    1. MacOS: darwin

    2. Linux: gnu/linux

    3. MS, windows-nt
Like

(if (eq system-type 'darwin)
  ; something for OS X if true
  ; optional something if not
)
--
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the EU and NATO membership of Ukraine.

>>> "JCvM" == John Ciolfi via Matlab-emacs-discuss <mat...@li...> writes:

> Yes, it's a good feature when working with scripts.
> The key binding is an issue I see too, though when using VNC.
> Sometimes the super key isn't passed through. It's also common for the
> windows super key to not work on Windows, see
> https://answers.microsoft.com/en-us/windows/forum/all/windows-key-not-working/0c796f79-0aa8-466e-ab44-802005d1791b
> which gives 8 methods for fixing that. I've hit this in the past.

> What about:

>     (define-key map (kbd "C-c C-<down>") #'matlab-sections-forward-section)
>     (define-key map (kbd "C-C C-<up>") #'matlab-sections-backward-section)
>     (define-key map (kbd "C-C C-<left>") #'matlab-sections-beginning-of-section)
>     (define-key map (kbd "C-C C-<right>") #'matlab-sections-end-of-section)
>     (define-key map (kbd "C-c M-<up>") #'matlab-sections-move-section-up)
>     (define-key map (kbd "C-c M-<down>") #'matlab-sections-move-section-down)
>     (define-key map (kbd "C-c M-<return>") #'matlab-sections-run-till-point)
>     (define-key map (kbd "C-c C-SPC") #'matlab-sections-mark-section)

Do you mean: in addition to the current keybinding setting or replacing
the  current keybinding?

If the current keybinding is problematic for Linux users, can't we
distinguish between the two or say  OS.

    1. MacOS: darwin

    2. Linux: gnu/linux

    3. MS, windows-nt
Like 

(if (eq system-type 'darwin) 
  ; something for OS X if true
  ; optional something if not
)
-- 
I strongly condemn Hamas heinous despicable pogroms/atrocities on Israel
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the EU and NATO membership of Ukraine. 

Yes, it's a good feature when working with scripts.

The key binding is an issue I see too, though when using VNC. Sometimes the super key isn't passed through. It's also common for the windows super key to not work on Windows, see https://answers.microsoft.com/en-us/windows/forum/all/windows-key-not-working/0c796f79-0aa8-466e-ab44-802005d1791b which gives 8 methods for fixing that. I've hit this in the past.

What about:

    (define-key map (kbd "C-c C-<down>") #'matlab-sections-forward-section)
    (define-key map (kbd "C-C C-<up>") #'matlab-sections-backward-section)
    (define-key map (kbd "C-C C-<left>") #'matlab-sections-beginning-of-section)
    (define-key map (kbd "C-C C-<right>") #'matlab-sections-end-of-section)
    (define-key map (kbd "C-c M-<up>") #'matlab-sections-move-section-up)
    (define-key map (kbd "C-c M-<down>") #'matlab-sections-move-section-down)
    (define-key map (kbd "C-c M-<return>") #'matlab-sections-run-till-point)
    (define-key map (kbd "C-c C-SPC") #'matlab-sections-mark-section)

Eric - another issue is that there are many files, including files shipped with MATLAB such as matlab/toolbox/matlab/uitools/uitools/msgbox.m which have %% characters that aren't sections and we get odd bolding as shown below. We also see odd bolding when %% are used and there are functions in the script. Nidish and I have been discussing this in https://github.com/mathworks/Emacs-MATLAB-Mode/issues/14. Maybe you have some thoughts on how to improve this? If we had better semantic understanding in matlab-sections.el, perhaps we could better understand where the sections are?

function varargout=msgbox(varargin)
%MSGBOX Message box.
%   msgbox(Message) creates a message box that automatically wraps
%   Message to fit an appropriately sized Figure.  Message is a string
%   vector, string matrix or cell array.
%

<snip>

%%%%%%%%%%%%%%%%%%%%
%%% Nargin Check %%%
%%%%%%%%%%%%%%%%%%%%
narginchk(1,6);
nargoutchk(0,1);

%check for support in deployed web apps
matlab.ui.internal.NotSupportedInWebAppServer('msgbox');

________________________________
From: Eric Ludlam <eri...@gm...>
Sent: Tuesday, November 19, 2024 5:08 PM
To: matlab-emacs-discuss <mat...@li...>
Subject: [Matlab-emacs-discuss] matlab-sections.el

Hi all,

I missed the discussions about the new matlab-sections.el that was added to matlab-mode recently.  I like the idea, thanks Nidish for working on it.

I spent a little time trying it out and wanted to share a few thoughts:

* matlab-sections-break-face no longer inherits from font-lock-comment-face.   Why is that?  My %% comments really stand out now that they aren't comment colored.  I could customize, but it seems like comments should color as comments.

* Not everyone has a functional super-key.  I'm using Windows/cygwin and the windows key does Windows stuff. :(   Emacs guidelines says that C-<punctuation> is reserved as a prefix for minor modes.  While inconvenient to type, using C-% as a prefix for matlab-sections (that start with %) as a backup prefix could be handy.

Thanks
Eric

Hi all,

I missed the discussions about the new matlab-sections.el that was added to
matlab-mode recently.  I like the idea, thanks Nidish for working on it.

I spent a little time trying it out and wanted to share a few thoughts:

* matlab-sections-break-face no longer inherits from
font-lock-comment-face.   Why is that?  My %% comments really stand out now
that they aren't comment colored.  I could customize, but it seems like
comments should color as comments.

* Not everyone has a functional super-key.  I'm using Windows/cygwin and
the windows key does Windows stuff. :(   Emacs guidelines says that
C-<punctuation> is reserved as a prefix for minor modes.  While
inconvenient to type, using C-% as a prefix for matlab-sections (that start
with %) as a backup prefix could be handy.

Thanks
Eric

2005	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (3)
2006	Jan	Feb (5)	Mar	Apr	May	Jun (1)	Jul	Aug	Sep	Oct (1)	Nov	Dec
2007	Jan	Feb	Mar (1)	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec
2008	Jan	Feb	Mar	Apr	May (9)	Jun (1)	Jul (1)	Aug (3)	Sep (1)	Oct	Nov (1)	Dec
2009	Jan	Feb (4)	Mar	Apr	May (2)	Jun (1)	Jul (7)	Aug (1)	Sep (5)	Oct	Nov (6)	Dec (3)
2010	Jan	Feb (10)	Mar (12)	Apr (13)	May (2)	Jun (4)	Jul (4)	Aug (4)	Sep	Oct (4)	Nov (2)	Dec (4)
2011	Jan (11)	Feb	Mar (18)	Apr	May (1)	Jun (12)	Jul (10)	Aug (4)	Sep (4)	Oct (5)	Nov	Dec (10)
2012	Jan (4)	Feb (26)	Mar	Apr (1)	May	Jun (8)	Jul (3)	Aug (1)	Sep	Oct (14)	Nov (1)	Dec (2)
2013	Jan (5)	Feb (2)	Mar (2)	Apr (5)	May (3)	Jun	Jul (8)	Aug (4)	Sep	Oct (7)	Nov (2)	Dec (7)
2014	Jan (14)	Feb	Mar (6)	Apr	May (3)	Jun (2)	Jul (4)	Aug (3)	Sep (7)	Oct (9)	Nov (9)	Dec (5)
2015	Jan (2)	Feb (1)	Mar	Apr (2)	May (1)	Jun (10)	Jul (3)	Aug (4)	Sep (8)	Oct (1)	Nov (3)	Dec (3)
2016	Jan (12)	Feb (59)	Mar (23)	Apr (11)	May (4)	Jun (15)	Jul	Aug	Sep (9)	Oct (19)	Nov (12)	Dec (5)
2017	Jan (1)	Feb (5)	Mar (5)	Apr	May (2)	Jun	Jul (5)	Aug	Sep (3)	Oct (12)	Nov (15)	Dec
2018	Jan (7)	Feb (6)	Mar	Apr	May (1)	Jun	Jul (3)	Aug (2)	Sep (2)	Oct (4)	Nov	Dec
2019	Jan (2)	Feb (9)	Mar (4)	Apr (9)	May (1)	Jun (1)	Jul (1)	Aug (3)	Sep	Oct (2)	Nov (6)	Dec (5)
2020	Jan (9)	Feb	Mar (2)	Apr	May (1)	Jun (2)	Jul	Aug	Sep	Oct (3)	Nov (28)	Dec (5)
2021	Jan (11)	Feb (2)	Mar (2)	Apr (2)	May (15)	Jun (9)	Jul (11)	Aug (1)	Sep	Oct (2)	Nov	Dec (3)
2022	Jan (1)	Feb	Mar	Apr (9)	May (1)	Jun	Jul (1)	Aug (1)	Sep	Oct	Nov	Dec
2023	Jan	Feb	Mar	Apr (12)	May (4)	Jun	Jul (22)	Aug (3)	Sep	Oct (1)	Nov	Dec (14)
2024	Jan	Feb	Mar	Apr (17)	May (35)	Jun (1)	Jul (18)	Aug (31)	Sep (5)	Oct (18)	Nov (20)	Dec (9)
2025	Jan	Feb	Mar	Apr (1)	May (1)	Jun (1)	Jul	Aug	Sep	Oct	Nov	Dec

matlab-emacs-discuss Mailing List for MATLAB in Emacs

matlab-emacs-discuss — Discuss Emacs/MATLAB integration