mathworks / mathworks/MATLAB-extension-for-vscode

Persistent clickable Command History panel (like MATLAB Desktop)

Open
#311 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
435
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Summary
The MATLAB extension currently opens the Command Window as a terminal but provides no persistent, clickable command history view like MATLAB Desktop. Please add a Command History view (side panel) that lists past commands, supports click-to-execute in the Command Window, search/filter, and optional export.

Problem

  • The extension's Command Window is an integrated UI (not a normal terminal) and has no history view.
  • Users cannot click past commands to re-run them from a persistent side panel.

Requested behavior

  • Add a contributed view (viewsContainers/views) named "Command History" that lives in the Side Bar / Auxiliary Bar.
  • Each entry should be clickable to send the command to the MATLAB Command Window.
  • Support search, clear, and export (optional).
  • Honor active MATLAB connection and focus the Command Window when executing.

Context
I inspected the extension package.json and it has no "views"/"viewsContainers" contributions (only commands/keybindings/terminal profile). A persistent history view would greatly improve workflow parity with MATLAB Desktop.

Thanks.

Possibly links to this request https://github.com/mathworks/MATLAB-extension-for-vscode/issues/294

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the extension package.json, especially its existing commands, keybindings, and terminal profile contributions. Check the related request in issue #294 for context before deciding how the view should fit the extension. Done means a persistent Command History view exists, entries can be searched and clicked to execute in the MATLAB Command Window, and clear/export behavior is defined.

Written by the indexing model from the issue text.

Assessment

Tech stack
matlab, typescript, vscode
Domain
developer-experience, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.