Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Last executed command pinned whenever your terminal window is using split panes #16178

Closed
ItsNotMyFault opened this issue Oct 16, 2023 · 3 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@ItsNotMyFault
Copy link

Description of the new feature/enhancement

Add a "pinned message" in the top of a split terminal.

I run multiple developments projects at the same time and I'm often forgetting which split terminal is for which project.
I often have my terminal window split in 4 to rapidly access the "npm watchers" of each of my projects. However sometimes I forget which split pane is for which project and it's annoying.
I would like to know the last executed command in the terminal and from which directory this command has been executed from.
A pinned message in the top of the split pane would do very nicely.

Proposed technical implementation details (optional)

Whenever I run a command in a split terminal' I would like for the last command to be pinned in the top of this specific split terminal.

@ItsNotMyFault ItsNotMyFault added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 16, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 16, 2023
@zadjii-msft
Copy link
Member

FWIW, I think this is a great idea. We're actually already tracking this over at /dup #14754, though that one's hard to find. I thought I'd find it linked to #13445, I was wrong.

There's also similarly #4717 and #4800, for "pane titlebars" (similar, but also different).

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Oct 16, 2023
@ItsNotMyFault
Copy link
Author

Perfect, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants