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-

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

/emacstipstring.m toolbox/help.m toolbox/opentoline.m This can be tweaked as needed to help melpa. For example, we could update it to generate the ":files" value you need. Thanks John From: Uwe Brauer Sent: Wednesday, October 02, 2024 10:59 AM To: John Ciolfi Cc:

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

you need from a Makefile target? Would something like that help? Thanks From: Uwe Brauer Sent: Tuesday, October 01, 2024 3:49 PM To: John Ciolfi Cc: Matlab-emacs-discuss Subject: The Cleanup of the matlab files Hi John I am about to update melpa, now besides c

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]

means nice functionality is not present. One example is LSP which I'm currently working on. This gives code navigation to function definitions and more. Thanks John From: Uwe Brauer Sent: Monday, August 26, 2024 11:02 AM To: John Ciolfi Cc: Uwe Brauer ; matla

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)

: Saturday, August 24, 2024 11:14 AM To: John Ciolfi Cc: Uwe Brauer ; Eric Ludlam ; matlab-emacs-discuss Subject: [installation problems] (was: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted) >>> "JC" == John Ciolfi writes: > Hi >

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

e ran into security issues, which delayed me. Thanks for your help, John From: Uwe Brauer Sent: Wednesday, August 21, 2024 8:29 AM To: John Ciolfi Cc: Uwe Brauer; Eric Ludlam; matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] move -->github: rebase, and w

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

, 2024 10:48 AM To: John Ciolfi Cc: Uwe Brauer ; Eric Ludlam ; matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted >>> "JC" == John Ciolfi writes: Hi John > Thanks - soon (perhaps tomorrow), I'll

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

er Cc: John Ciolfi; Eric Ludlam; matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted > I have also quite a bit of clones, so no worries. > Here is what I did on my local machine (I did not mess up wi

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

4 11:52 AM To: John Ciolfi Cc: Uwe Brauer; Eric Ludlam; matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] move -->github: rebase, and which branches could be deleted >>> "JC" == John Ciolfi writes: > Hi > I just double checked the fontlonkhang branch, dow

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

hangs we were seeing no longer exist. I believe what happened is that Eric and I used the fontlockhang as a "staging" area and then once solved, we manually added to master. Thanks John From: Uwe Brauer Sent: Thursday, August 01, 2024 4:46 PM To: John

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

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

he history from the main branch, then people with other branches could choose to create new forks in github with their changes. Regardless, we should keep the Source Forge reference in the github repo. Thanks John From: Uwe Brauer Sent: Monday, July 29, 2024 1

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

s that okay? thanks John From: Uwe Brauer Sent: Monday, July 29, 2024 11:21 AM To: John Ciolfi Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net; Nidish Narayanaa Balaji Subject: Re: Move of matlab-mode from Source Forge to github >>> "JC"

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

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

r Sent: Tuesday, July 16, 2024 10:58 AM To: John Ciolfi Cc: matlab-emacs-discuss@lists.sourceforge.net ; Uwe Brauer ; Nidish Narayanaa Balaji Subject: Re: Move of matlab-mode from Source Forge to github >>> "JC" == John Ciolfi writes: hi > Hi > We'd like

[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]

Sent: Wednesday, May 22, 2024 2:18 PM To: John Ciolfi ; Uwe Brauer Cc: matlab-emacs-discuss@lists.sourceforge.net Subject: Re: [Matlab-emacs-discuss] [font-lock stopped working] [fixed] Hello John, Thank you for taking a look! By "Cells" I don't mean the matlab cell ob

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] t

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 &qu

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

s the existing mlint Thanks John From: Uwe Brauer Sent: Friday, December 29, 2023 11:43 AM To: John Ciolfi Cc: Uwe Brauer ; Matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] new branches, plans, rename development branch to default, mirror to github &g

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

Re: [Matlab-emacs-discuss] issue with figure generated by a matlab org src block

Hi If you have the latest https://sourceforge.net/projects/matlab-emacs/, take a look at https://sourceforge.net/p/matlab-emacs/src/ci/master/tree/examples/matlab-and-org-mode/matlab-and-org-mode.org This should get matlab working with Emacs nicely (we use this with Emacs 27 and it works for u

Re: [Matlab-emacs-discuss] [a mess of GPL versions]

Hi I should have some time the week after next to help organize what files should be shipped with matlab mode. I'd like to get https://github.com/mathworks/MATLAB-language-server setup as part of this. Many of us have been using an internal version of this in Emacs and like it a lot. It provid

Re: [Matlab-emacs-discuss] another bug with the filling alorithm

Hi Uwe, Eric fixed the issue, see attached patches which apply against the current source forge tip, 3048e9. I also tested it and have deployed it internally within MathWorks. Can you try the patches and if they are good, update source forge? Thanks, John From:

Re: [Matlab-emacs-discuss] filling of very long inline comments

I took a quick look. matlab-fill-comment-line assumes that it is filling a comment only line and not a trailing comment. I'm not as familiar with the code as Eric. Eric would you have a chance to look at this? Also, I've noticed that M-q doesn't work on some comments. For example, given the fol

Re: [Matlab-emacs-discuss] matlab-mode, electric-pair-mode and the single quote (')

d get electric pair mode working. From: Uwe Brauer Sent: Tuesday, April 26, 2022 2:24 AM To: Peter Mao Cc: John Ciolfi; matlab-emacs-discuss Subject: Re: [Matlab-emacs-discuss] matlab-mode, electric-pair-mode and the single quote (') >>> "PM"

Re: [Matlab-emacs-discuss] matlab-mode, electric-pair-mode and the single quote (')

There was a recent fix to the syntax class for the single quote, https://sourceforge.net/p/matlab-emacs/src/ci/a5e88cda8e0715f117f09e6101f39302387f2d6b/ I'm not familiar with electric pair mode but tried it and it seems to work for the case you mentioned. Some downsides I noticed with it was (2)

Re: [Matlab-emacs-discuss] completion and goto-function in matlab-mode (Doom emacs)

is process works. Thanks John From: Uwe Brauer Sent: Monday, November 30, 2020 11:29 AM To: John Ciolfi Cc: Eric Ludlam; Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net Subject: Re: [Matlab-emacs-discuss] completion and goto-function in matlab-mode (Doom emacs

Re: [Matlab-emacs-discuss] completion and goto-function in matlab-mode (Doom emacs)

Hi Uwe, Some items to test: * The handling of *.m files. matlab.el used to contain: (add-to-list 'auto-mode-alist '("\\.m$" . matlab-mode)) which overrides the Emacs default of associating *.m files with objc-mode. This setting means it isn't possible to edit in objc-mode for *.m objectiv

Re: [Matlab-emacs-discuss] Clear matlab command buffer

Hi Could it be due to very long lines (not the number of lines)? Do you have an example, maybe a MATLAB script I could run to take a look at the issue? Thanks On Nov 20, 2020, at 2:50 PM, Karthik Chikmagalur wrote:  Hi Jiaen, Matlab-shell is derived from comint-mode, so you can use "C-c M-

Re: [Matlab-emacs-discuss] annoying path behavior of the *MATLAB* shell buffer who is the culprit

I wonder if we could update matlab mode to ask what cwd is each time it sees the prompt? On Feb 24, 2017, at 1:26 PM, Uwe Brauer wrote: "Eric" == Eric Ludlam writes: > >> Hiya, >> Matlab-shell uses dirtrack, or shell-directory-tracker. It just >> watches the input stream and changes defa

Re: [Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

I put my changes on the github mirror in a proposed changes branch and requested a pull. Thanks From: Eric Ludlam Sent: Tuesday, October 11, 2016 2:26:06 PM To: Uwe Brauer; John Ciolfi Cc: matlab-emacs-discuss@lists.sourceforge.net Subject: RE: [Matlab-emacs

Re: [Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

o when it stops. The warnings fixes shouldn't have altered Xemacs, but I didn't test Xemacs. Thanks John From: Uwe Brauer Sent: Monday, October 10, 2016 3:48:41 PM To: John Ciolfi Cc: matlab-emacs-discuss@lists.sourceforge.net Subject: Re: [Matla

Re: [Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

Got it. Thanks. I'll try pushing the changes tonight. From: Uwe Brauer Sent: Monday, October 10, 2016 4:58:26 PM To: John Ciolfi Cc: Uwe Brauer; matlab-emacs-discuss@lists.sourceforge.net Subject: Re: [Matlab-emacs-discuss] Fixes for tab completion, debuggi

Re: [Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

correctly ;; ;; >> !touch foo.ext1 foo.ext2 ;; >> ! mv foo. Should give options foo.ext1 foo.ext2 ;; >> ! mv foo.ext1 Should say no completions ;; >> ! mv foo.ext1 Should say no completions (note the space before the TAB) ;; ;; >&

Re: [Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

On github, my id is JohnC32 (I don't have one on source forge) and have only used the github id to comment a couple times, so I have a little learning to do. Thanks John From: Uwe Brauer Sent: Monday, October 10, 2016 4:36:56 PM To: John Ciolfi Cc: Uwe B

[Matlab-emacs-discuss] Fixes for tab completion, debugging in with R2015b and later

Hi I have the following updates, but can send zip files or the diff -r -u output (zip's aren't allowed and the diff -r -u is too long). Any thoughts on how I could get these into the source forge repo? 1. Fixed several problems with TAB completion, and added direct support for company (comp

Re: [Matlab-emacs-discuss] compiler warnings

___ From: Uwe Brauer Sent: Friday, September 2, 2016 8:09 AM To: John Ciolfi Cc: matlab-emacs-discuss@lists.sourceforge.net Subject: Re: [Matlab-emacs-discuss] compiler warnings >>> "John" == John Ciolfi writes: > I just updated to the latest matlab emacs and see a fe

[Matlab-emacs-discuss] compiler warnings

I just updated to the latest matlab emacs and see a few warnings. I realize some of these are to support older emacs's but some look like they could be fixed (and maybe suppress the others for older releases)? I'm building on Debian 8 using emacs 24.4.1 Thanks John In matlab-with-emacs-link

[Matlab-emacs-discuss] typo in tlc-mode

? In tlc.el, there's a missing space which results in an error: ;;;###autoload(add-to-list 'auto-mode-alist '("\\.tlc$" .tlc-mode)) a space is needed between the '.' and 'tlc', i.e. ;;;###autoload(add-to-list 'auto-mode-alist '("\\.tlc$" . tlc-mode)) Could someone fix? Thanks ---