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

Way to lock/pin tabs #8007

Closed
Nosamdaman opened this issue Oct 22, 2020 · 5 comments
Closed

Way to lock/pin tabs #8007

Nosamdaman opened this issue Oct 22, 2020 · 5 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

@Nosamdaman
Copy link

Description of the new feature/enhancement

I think a feature that would allow a user to "lock" a tab or whole window could be extremely useful. If I'm running a particularly long command/job in a remote session for example, being able to lock that tab so that no input could be sent to the tab would help prevent accidental cancelations if the window regained focus without me knowing it. It would then also be nice if the close window/tab button popped up a warning or confirmation dialogue when attempting to close the tab/window in question regardless of the confirmCloseAllTabs option when a locked or pinned tab is present. Using this feature in combination with the always on top mode would be a great way to ensure that you could monitor the progress of jobs without having to worry about accidentally interfering with them.

Proposed technical implementation details (optional)

@Nosamdaman Nosamdaman added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Oct 22, 2020
@ghost ghost 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 22, 2020
@ghost
Copy link

ghost commented Oct 22, 2020

dup of #5969

@Nosamdaman
Copy link
Author

Ah, I didn't see that when writing this issue. Though I'd still argue that the locking of inputs makes this at least somewhat a separate feature.

@ghost
Copy link

ghost commented Oct 22, 2020

That is a /dup of #6981

@Nosamdaman
Copy link
Author

So it is. Thanks, I guess I was just searching with the wrong keywords.

@ghost
Copy link

ghost commented Oct 22, 2020

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!

@ghost ghost 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 22, 2020
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

1 participant