mathworks / mathworks/MATLAB-extension-for-vscode
MATLAB External Source Control Integration does not use VSCode MATLAB session
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 435
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
When launching the simulink difftool via command-line (see [1]), a new session of MATLAB is opened rather than the existing session of MATLAB used by VSCode.
This is not useful as this means paths are not setup appropriately and it results in missing subsystem references.
Describe the solution you'd like
When launching the simulink difftool via command-line, the existing instance of MATLAB used by VSCode would be used to avoid opening a new MATLAB process.
Example command using the mlDiff definition in [1]: git difftool --no-prompt -t mlDiff origin/master -- Model/fileA.slx
Describe alternatives you've considered
Opening MATLAB separate from VSCode works without issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue description and the MathWorks external source-control documentation linked there, then reproduce the git difftool --no-prompt -t mlDiff origin/master -- Model/fileA.slx workflow from VS Code. Trace how the extension's MATLAB session is launched or exposed; done means the Simulink difftool reuses the VS Code MATLAB instance instead of opening a separate process and retains configured paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- matlab, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100