Re: [Matlab-emacs-discuss] matlab-sections.el

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 >>> writes: > Yes, it's a good feature when working with

Re: [Matlab-emacs-discuss] matlab-sections.el

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-ke

Re: [Matlab-emacs-discuss] matlab-load.el-->matlab-autoload.el

I'm good with this. Why does melpa need matlab-autoload.el? Also update references to matlab-load find . -type f -exec grep -l matlab-load {} \; ./Makefile ./README.org ./examples/matlab-and-org-mode/matlab-and-org-mode.html ./examples/matlab-and-org-mode/matlab-and-org-mode.org ./tests/mstest.e

Re: [Matlab-emacs-discuss] version numbering and copyright dates

I think it's okay to leave them as is. Updating when the files change should be simpler and what is legally required. Thanks From: Uwe Brauer Sent: Sunday, October 06, 2024 2:57 AM To: John Ciolfi Cc: Matlab-emacs-discuss; Uwe Brauer Subject: Re: [Matlab-emacs-d

Re: [Matlab-emacs-discuss] version numbering and copyright dates

Hi Copyright years should only be updated when there is a material change. For example, suppose foo.el was authored in 2010 and not touched. Its copyright year should stay 2010. If foo.el then get's updated in 2025, it's copyright year would become 2010-2025. We could probably automate this.

Re: [Matlab-emacs-discuss] follow Jonas advice for the MELPA package in sourceforge.

That seems reasonable. It would be good to get MELPA pointing at github because the version in github works with later Emacs versions (I removed some of the .el files that no longer work). thanks From: Uwe Brauer via Matlab-emacs-discuss Sent: Friday, October 4

Re: [Matlab-emacs-discuss] The Cleanup of the matlab files

I just added a make target to help with this (commit ccd2d06): make list-files-for-release which will display the following (notice matlab-load.el is excluded because this is generated and dependent on the version of Emacs): company-matlab-shell.el linemark.el matlab-cgen.el matlab-compat.e

Re: [Matlab-emacs-discuss] update to Matlab2024b: can't compile

Hi This is fixed (commit 59bf9a9 - Update tests/mstest.el to work with R2024b). Thanks John From: Uwe Brauer via Matlab-emacs-discuss Sent: Tuesday, October 1, 2024 4:42 AM To: Matlab-emacs-discuss Subject: [Matlab-emacs-discuss] update to Matlab2024b: can't co

Re: [Matlab-emacs-discuss] The Cleanup of the matlab files

Hi We need the *.el files and all *.m files under the toolbox directory tree, and the bin/*.sh file. cd Emacs-MATLAB-Mode ls *.el find toolbox -name '*.m' -print ls bin/*.sh Note, the bin/*.sh is used by one of the *.m files. I wonder if there's a way to generate what you need from a

Re: [Matlab-emacs-discuss] change targets makefile

Hi Good point on the NOTESTS=1 - that's confusing and actually redundant as we already have tests target, so I simplified the Makefile and updated README.org section on building: cd /path/to/Emacs-MATLAB-mode # Build lisp and run tests (requires MATLAB executable): make # Alternatively

[Matlab-emacs-discuss] Dropping support for Emacs 26 and prior

Hi I'd like to fix the various Emacs lisp compiler warnings and also drop support for Emacs 26 and prior. Dropping Emacs 26 makes it easier to add new features. Emacs 26 was released on May 28, 2018. If someone needs Emacs 26 or prior, please let us know also we'd like some help keeping Emacs

Re: [Matlab-emacs-discuss] Emacs Matlab Nerd-Icons missing

Hi We've moved development of matlab-mode to https://github.com/mathworks/Emacs-MATLAB-Mode Can you create an issue there? Thanks John From: Vasco Cúrdia Sent: Monda

Re: [Matlab-emacs-discuss] problems with the actual (and earlier Makefiles) for emacs 29.2

Hi In https://github.com/MathWorks/Emacs-MATLAB-Mode, we've deleted cedet-matlab.el because it no longer works and there's a better replacement - LSP, which I will try to get in place soon. As for the autoload issue, I just made a new commit that fixes that. I also just added make -f check-ema

Re: [Matlab-emacs-discuss] [installation problems]

earlier..... BTW, I saw, you removed emacs 26 support. Shouldn't we discuss on the list? I don't mind and I also don't have the impression that it would effect many users, but just in case, what do you think? > Thanks > John > > From: John Ci

Re: [Matlab-emacs-discuss] [installation problems] (was: move -->github: rebase, and which branches could be deleted)

: John Ciolfi via Matlab-emacs-discuss Sent: Saturday, August 24, 2024 12:44 PM To: Uwe Brauer Cc: matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] [installation problems] (was: move -->github: rebase, and which branches could be deleted) I’ll look at this in a couple of days. I can conf

Re: [Matlab-emacs-discuss] [installation problems] (was: move -->github: rebase, and which branches could be deleted)

I’ll look at this in a couple of days. I can confirm the tests pass on Debian 12 with Emacs 28 using R2024a. The code should match source forge minus some stale code that no longer works. So, this is likely an existing issue Thanks John From: Uwe Brauer Sent:

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

Hi I setup https://github.com/mathworks/Emacs-MATLAB-Mode per your guidelines where I deleted the old branches, then mirrored. I then added a commit (reviewed a while back by Eric): Cleanup stale files and setup to align with github MathWorks standards 1. For MathWorks standards, - Renamed

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

Hi Sorry for the delay. I’m out on vacation but will try to finish this in the next day or so. It took a little longer than I expected to get things setup, but now I have the right permissions to do this. Thanks John From: Uwe Brauer Sent: Tuesday, August 20,

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

Thanks - soon (perhaps tomorrow), I'll try to set up the empty github area so you can push the history to it. I need to talk with some people in MathWorks on how to do this. Thanks, John From: Uwe Brauer Sent: Tuesday, August 13, 2024 8:43 AM To: Uwe Brauer Cc:

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

I think Eric may be on vacation. I'm fairly confident that we've already taken the work from shellcomplete and put it in master. Just in case we haven't, I just made a git clone of matlab-emacs that contains all the current branches. I'll double check with Eric when he's back. I too am about to

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

I took a quick look at shellcomplete and think master is more current. There's a fair bit of diff in matlab-complete.el and master looks more current. Around the time of the branch activity, Eric and I were improving matlab completion and I think we used this branch a little, then directly sent

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

Hi I just double checked the fontlonkhang branch, downloaded zip * matlab-emacs-src-a78b368387c85437f8de187acf0a2b1cbeeacc3f/ (master) * matlab-emacs-src-ce22c697d06ece776cfd7a9a41b3704f1815823f/ (fontlockhang) And diff'd them - all changes are in master. I also validated that the hangs we

Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted

Regarding the fontlockhang, these have been merged in to the main/master branch already. I just manually compared matlab.el between and the fontlock improvements are in the tip. The fontlockhang branch can be deleted. Note, in MathWorks we are using the current matlab-emacs tip minus a few item

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Great, if you can help me get this in place (clean history and the 'default' branch), I will up get it uploaded to github. Thanks John From: Uwe Brauer Sent: Monday, July 29, 2024 4:11 PM To: John Ciolfi Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Hi I'm proposing starting fresh meaning initially no history in github. You'd need to jump back to Source Forge for the older changes. They would not be lost. We'd freeze Source Forge and add a link to them. Part of the reason for doing this is that there is a bunch of old stuff in Source Forge

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

To be clear on the proposal, I would place the latest version matlab-mode in github with a reference to the project history in Source Forge in the main README.org file From: John Ciolfi via Matlab-emacs-discuss Sent: Monday, July 29, 2024 12:50 PM To: Uwe

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Hi I haven't spent time looking into how to make the branch 'default' (too many other items on my plate) Once that's done, I can upload the repo to github. My original proposal was to start fresh in github and keep the older history in Source Forge as this is simpler. Is that okay? thanks John

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Okay, I'll look into seeing if we can call it default. Thanks From: Uwe Brauer Sent: Wednesday, July 17, 2024 2:32 PM To: John Ciolfi Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net; Nidish Narayanaa Balaji Subject: Re: Move of matlab-mode from Source

Re: [Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Hi For the main branch, the convention is to use "main" in github. I'm not sure if there's a way to switch from that. If possible, I'd like to use that. Here's an example of a MathWorks sponsored project, https://github.com/mathworks/MATLAB-language-server. As a side note, I have the MATLAB l

[Matlab-emacs-discuss] Move of matlab-mode from Source Forge to github

Hi We'd like to move matlab-mode from Source Forge to github, https://github.com/MathWorks/Emacs-MATLAB-Mode, which gives us a good location for the "master" matlab-mode in github along with the benefits of github. Note, there are already many copies of matlab-mode in other github areas. The p

Re: [Matlab-emacs-discuss] [font-lock stopped working] [fixed]

Ah - I forgot we call the %% sections "cells". Perhaps a better name would be code sections, https://www.mathworks.com/help/matlab/matlab_prog/create-and-run-sections.html I'll re-look at this soon. Thanks John From: Nidish Narayanaa Balaji Sent: Wednesday, M

Re: [Matlab-emacs-discuss] [font-lock stopped working] [fixed]

Hi I like the idea of speedy navigation of cells. I took a brief look at the matlab-cell branch but wasn't sure what it's supposed to be used for. The first thing I tried was navigating a large cell argument to a function, something like: a = fun( { Big cell }, { Another cell .

Re: [Matlab-emacs-discuss] [another problem] (was: the filling patch and its problems)

Ouch, that's bad, we'll need to keep this as an open issue. Thanks John From: Uwe Brauer Sent: Wednesday, May 22, 2024 4:28 AM To: John Ciolfi Cc: Uwe Brauer; Matlab-emacs-discuss; Eric Ludlam Subject: [another problem] (was: [Matlab-emacs-discuss] the filling pa

Re: [Matlab-emacs-discuss] the filling patch and its problems

-up. I tried M-q in a *.cpp file for a similar case and it requires only one M-q. Are there any other cases that behave poorly? Thanks From: John Ciolfi via Matlab-emacs-discuss Sent: Tuesday, May 21, 2024 10:35 AM To: Uwe Brauer Cc: Matlab-emacs-discuss

Re: [Matlab-emacs-discuss] the filling patch and its problems

It looks like we have more work to do and they are not ready. Thanks From: Uwe Brauer Sent: Tuesday, May 21, 2024 9:39 AM To: John Ciolfi Cc: Eric Ludlam; Uwe Brauer; Matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] the filling patch and its problems "JC"

Re: [Matlab-emacs-discuss] the filling patch and its problems

Hi Uwe, I don't think these fill-paragraph patches made it into master. Attached are the patches that work for me. Are there any reasons to not apply them? Thanks, John From: Uwe Brauer Sent: Monday, July 31, 2023 11:57 AM To: Eric Ludlam Cc: Matlab-emacs-di

Re: [Matlab-emacs-discuss] new branches, plans, rename development branch to default, mirror to github

How about we use emacs-matlab-mode and on the main page indicate it is now the primary devel location replacing source forge, though we'll still use the source forge mailing lists, which we can list. Let me investigate the best username to use for GitHub . I think it would be good to add the re

Re: [Matlab-emacs-discuss] new branches, plans, rename development branch to default, mirror to github

Thanks Uwe, having development on github will help. I have a few items I'd like to contribute but have been too busy to polish them off. Moving to github will make that easier because I'm more familiar with it. From: Uwe Brauer Sent: Thursday, December 28, 2023 1