Skip to content

Should keeping the "current" editor dismiss and no-op? #122433

New issue
New issue
Closed
Closed
Should keeping the "current" editor dismiss and no-op?#122433
Assignees
lramos15
Labels
feature-requestRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code Insidersverification-neededVerification of issue is requestedverifiedVerification succeededworkbench-editor-resolverIssues resolving the editor inputs
Milestone
May 2021
@connor4312

Description

@connor4312
connor4312
opened on Apr 27, 2021

Testing #122030

I like to keep my settings file clean-ish, when possible. If the editor for a new opened file is already what I want, we could store a "dismiss" in global storage and not write anything to the settings file.

Metadata

Metadata

Assignees

Labels

feature-requestRequest for new features or functionalityinsiders-releasedPatch has been released in VS Code Insidersverification-neededVerification of issue is requestedverifiedVerification succeededworkbench-editor-resolverIssues resolving the editor inputs

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions